You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I was looking through the package.json in the root and I see the app requires >= 14.0.0. If this is not put in the .npmrc as engine-strict=true that rule is not applying across the project. A perfect example is when I run pnpm install I get the following error when adding engine-strict=true
cloud spacedrive [npmrc] pnpm install
Scope: all 13 workspace projects
Lockfile is up to date, resolution step is skipped
ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)
Your Node version is incompatible with "/amqplib/0.5.2".
Expected version: >=0.8 <=9
Got: v14.19.2
Please also reference the PNPM doc PNPM Package.json which goes over the difference of when using engine requirements. I feel for consistency this would be better suited in .npmrc so we can avoid any packages being added that are not compatible with the required node. We may want to update the package.json to be consistant with CONTRIBUTE.md which references the need for Node Version: 17
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
So I was looking through the package.json in the root and I see the app requires >= 14.0.0. If this is not put in the .npmrc as engine-strict=true that rule is not applying across the project. A perfect example is when I run pnpm install I get the following error when adding engine-strict=true
cloud spacedrive [npmrc] pnpm install
Scope: all 13 workspace projects
Lockfile is up to date, resolution step is skipped
ERR_PNPM_UNSUPPORTED_ENGINE Unsupported environment (bad pnpm and/or Node.js version)
Your Node version is incompatible with "/amqplib/0.5.2".
Expected version: >=0.8 <=9
Got: v14.19.2
Please also reference the PNPM doc PNPM Package.json which goes over the difference of when using engine requirements. I feel for consistency this would be better suited in .npmrc so we can avoid any packages being added that are not compatible with the required node. We may want to update the package.json to be consistant with CONTRIBUTE.md which references the need for Node Version: 17
Beta Was this translation helpful? Give feedback.
All reactions