Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DX] Improve error when added module is no module #15166

Closed
3 of 4 tasks
manniL opened this issue Oct 14, 2022 · 0 comments · Fixed by nuxt/framework#8198
Closed
3 of 4 tasks

[DX] Improve error when added module is no module #15166

manniL opened this issue Oct 14, 2022 · 0 comments · Fixed by nuxt/framework#8198

Comments

@manniL
Copy link
Member

manniL commented Oct 14, 2022

Describe the feature

When adding a npm package to modules that actually is not a Nuxt module (but e.g. exports CSS), the error message is rather cryptic:

e.g. ERROR Cannot start nuxt: expected expression, got ':' 15:56:50

It would be nice to provide a more readable warning and also hint that the module that is failing might not be a module.

Repro

Additional information

  • Would you be willing to help implement this feature?
  • Could this feature be implemented as a module?

Final checks

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

Successfully merging a pull request may close this issue.

2 participants