Chore: Fix build:docs&build:registry script loop & add engines field for consistency #806
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR focuses on fixing a script recursion issue in the root
package.jsonand ensuring consistent runtime environments across the workspace.Because stability is the priority, this fix introduces a minor but important adjustment.
Changes
build:docsto useturbo run build:docs --filter=@magicui/wwwinstead of recursively calling
pnpm build:docs, which caused an infinite loop at the root level.build: registryto useturbo run build: registry --filter=@magicui/wwwinstead of recursively calling
pnpm build: registry, which caused an infinite loop at the root level.enginesfield to the rootpackage.jsonto enforce Node>=22.14.0and pnpm>=9, aligning with the app configuration.Motivation
pnpm build:docsfrom the root.pnpm build:registryfrom the root.Breaking Changes
turbo run …) when invokingbuild:docsfrom the root.