-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
CLI: Add support for Nuxt framework #23663
base: next
Are you sure you want to change the base?
Conversation
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
Co-authored-by: Yann Braga <yannbf@gmail.com>
@chakAs3 please add detailed "What I did" and "How to test". |
thanks, @ndelangen and @yannbf for the quick review, i did not yet finish I'm adding some description and cleaning up |
yes but this version is creating a conflict for me for some reason, that is why i had to change however i have other solution i will add it the |
Co-authored-by: Yann Braga <yannbf@gmail.com>
…book into chaks/cli-nuxt
@chakAs3 Is this one ready to be reviewed? |
I checked it out. It seems like the template directory is missing: I do see it is here, but maybe somehow ignored when publishing to npm? |
no it is there maybe not the last version . let me update deps |
…book into chaks/cli-nuxt
…chaks/cli-nuxt
Any updates on this PR? What does it need to get it merged? |
Hi @valentinpalkovic i have get back on it. it is been 2 months |
Closes #
What I did
I added support for NUXT project to the CLI,
How to test
To create repo template run
yarn task --task generate --template nuxt-vite/default-ts
To create sandbox from template:
yarn task --task sandbox --template nuxt-vite/default-ts
For init run inside Nuxt project
'yarn storybook init
or
npx storybook@next init`Checklist
MIGRATION.MD
Maintainers
ci:normal
,ci:merged
orci:daily
GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.ts
["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]
🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/core
team here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>