Published package shouldn't have packageManager or engines fields
#15
Comments
|
I think you are right about |
|
I tried it out with the packageManager as well, and it fails on
codesandbox and stackblitz as both run on pnpm 8.x
…On Wed, 19 Feb 2025 at 07:43, Damian Tarnawski ***@***.***> wrote:
I think you are right about engines but I think packageManager is fine
and it only affects if you use a package manager in the same directory. But
I would need to confirm that.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVSGJ3LD73SUOENQERLCCD2QQR25AVCNFSM6AAAAABXM2DJEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXGYZTSNZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: thetarnav]*thetarnav* left a comment
(solidjs-community/solid-motionone#15)
<#15 (comment)>
I think you are right about engines but I think packageManager is fine
and it only affects if you use a package manager in the same directory. But
I would need to confirm that.
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAVSGJ3LD73SUOENQERLCCD2QQR25AVCNFSM6AAAAABXM2DJEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNRXGYZTSNZWGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the following in package.json is not advised as it's not a node runtime package. This breaks usage in basically all environments as
npm installorpnpm installwill fail, for instance on Stackblitz.npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '[email protected]', npm WARN EBADENGINE required: { node: '>=20', pnpm: '>=9.0.0' }, npm WARN EBADENGINE current: { node: 'v18.20.3', npm: '10.2.3' } npm WARN EBADENGINE }More info:
nodejs/corepack#485
The text was updated successfully, but these errors were encountered: