Skip to content

Conversation

@stepan-twnty
Copy link

@stepan-twnty stepan-twnty commented Sep 26, 2025

Description

In the docs mentioned .nuxt/tsconfig.json - Legacy configuration for backward compatibility

Type of change

ToDo's

Screenshots (if applicable)

Additional context

With the old config, I had a problem with types in WebStorm

@vercel
Copy link

vercel bot commented Sep 26, 2025

@stepan-twnty is attempting to deploy a commit to the Shopware Frontends Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
Copy link

vercel bot commented Oct 6, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
shopware-frontends-docs Ready Ready Preview Oct 6, 2025 10:57am

Copy link
Contributor

@patzick patzick left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good direction!

  1. Unfortunately there's a typo - missing comma atfer the "include"
  2. after that IDE tells that there's something wrong with the settings, any idea why? (screen)
  3. would be great to also add this to vue-starter-template when it starts working with no errors
Image

Copy link
Contributor

@mkucmus mkucmus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

currently we've got a weird situation that project references are the recommended future approach, but type checking currently requires the legacy format.

the community encountered some issues due to new references format in nuxt 4:

nuxt typecheck will fail with the new config. I think we need to wait until the issue is fixed and then we can migrate entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants