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

chore: rename dev:prepare to prepare #156

Closed
wants to merge 2 commits into from

Conversation

tobiasdiez
Copy link

Since the tsconfig in the root references the tsconfig of the playground, one has to call nuxi prepare playground before running everything else. In particular, it is needed before prepack. Renaming dev:prepare to prepare takes care of this automatically.

@codesandbox
Copy link

codesandbox bot commented Nov 11, 2022

CodeSandbox logoCodeSandbox logo  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

@danielroe
Copy link
Member

The reason this is not named prepare is because of an npm bug that, in some circumstances, runs prepare immediately before packing, meaning that even if you build the project in a prepack step, the built files are then replaced with stubs in the tarball.

@pi0
Copy link
Member

pi0 commented Nov 14, 2022

Thanks for PR. Another issue is that prepare runs during release process (on packing).

I understand that it is not best command but is one time only. Later we shall improve module builder and nuxi to automate prepare.

@pi0 pi0 closed this Nov 14, 2022
@tobiasdiez tobiasdiez deleted the patch-2 branch November 14, 2022 19:10
tobiasdiez added a commit to tobiasdiez/nuxt-graphql-server that referenced this pull request Mar 4, 2023
Fixes #34.

Prepare is not the correct hook as discussed in nuxt/starter#156.
tobiasdiez added a commit to tobiasdiez/nuxt-graphql-server that referenced this pull request Mar 4, 2023
Fixes #34.

Prepare is not the correct hook as discussed in nuxt/starter#156.
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.

None yet

3 participants