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

'The entry point "vue" cannot be marked as external' after installing Nuxt Storybook module #656

Closed
MooseSaeed opened this issue Jun 17, 2024 · 4 comments

Comments

@MooseSaeed
Copy link

Description:

I encountered an issue after installing the Nuxt Storybook module in a new Nuxt project. Upon running yarn dev, the following error appears in the console:

✘ [ERROR] The entry point "vue" cannot be marked as external

Steps to Reproduce:

  1. Create a new Nuxt project using npx nuxi@latest init my-project
  2. Navigate to the project directory: cd my-project
  3. Install the Nuxt Storybook module: npx nuxi@latest module add storybook
  4. Run the development server: yarn dev

Expected Behavior:

The Nuxt development server should start without errors, and the Storybook module should be correctly initialized.

Actual Behavior:

The storybook server fails to start, and the following error is shown in the console:

✘ [ERROR] The entry point "vue" cannot be marked as external

Repro:

https://github.com/MooseSaeed/test-nuxt

Additional Context:

I have not made any other changes to the default configuration of the new Nuxt project. This error appears to be directly related to the Nuxt Storybook module.

@blowsie
Copy link
Contributor

blowsie commented Jun 17, 2024

Me too, I found this related PR
#634
#641

@tobiasdiez
Copy link
Collaborator

Yes, this should be fixed in the main branch. It might take a couple of days until we release it. Alternatively, it should work if you downgrade nuxt to v 3.11.x

@MooseSaeed
Copy link
Author

@tobiasdiez I tried to downgrade nuxt to v 3.11 and 3.10 but still getting the same issue

@blowsie
Copy link
Contributor

blowsie commented Jun 19, 2024

Worked for me, be sure to remove a ^ symbol in the package json if you have one

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

No branches or pull requests

3 participants