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
Corepack inspects the package.json of an end-user's project, and, if packageManager is set, restricts invocation of other package managers. This works in most cases but fails when a package that project wants to install has a lifecycle script that hard-codes a package manager. In this case, npm run build-release.
Hey y'all! Because of the way the
install
script is configured forbetter-sqlite3
it doesn't always play nicely withcorepack
when a consumer is using a non-npm package manager.Corepack inspects the
package.json
of an end-user's project, and, ifpackageManager
is set, restricts invocation of other package managers. This works in most cases but fails when a package that project wants to install has a lifecycle script that hard-codes a package manager. In this case,npm run build-release
.There are multiple workarounds to this problem but they all have tradeoffs.
I'm hoping you'd be willing to consider making a change that adjusts the
install
script in yourpackage.json
. There are a number of options:"install": "prebuild-install || node-gyp rebuild --release"
"install": "prebuild-install || npm run build-release || yarn run build-release || pnpm run build-release"
"install": "prebuild-install || COREPACK_ENABLE_STRICT=0 npm run build-release"
What do you think?
The text was updated successfully, but these errors were encountered: