chore: add root .npmrc for consistent workspace dependency hoisting #71
+2
−0
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.
Problem Description
When running
pnpm installfrom the root directory, the dependency hoisting strategy may be inconsistent with subdirectory configurations, causing module resolution issues (e.g., dayjs import errors).fixed: #70
Solution
Add
.npmrcfile at the root level to unify pnpm configuration across the entire workspace:shamefully-hoist=true: Ensures dependencies are hoisted to thenode_modulesroot directory, compatible with Nuxt/Vite module resolution mechanismstrict-peer-dependencies=false: Allows flexible peer dependency resolution to avoid installation failuresImpact
pnpm installworks correctly when executed from the root directoryapps/www/.npmrcconfiguration