Closed mat-sz closed 2 months ago
It seems you're on linux-x64, so uou should have available binaries (see the table), making me believe this is happening because Yarn runs the postinstall script even when this is installed as a dependency, whereas NPM does not.
patch-package
is necessary for my usecase (there's an incompatibility in cmake-js
on Windows that's a bit weird to upstream), but I concur the usecase is niche. It and cmake-js
need to remain in the devDependencies because they should not be installed unless trying to build from source. I'll make a change to not make it a postinstall script (instead something like "patch" that Windows users can run (really the Windows build is much harder than this so I don't know why I bother)), should be fixed in the next release 👍
@mat-sz I've since released 0.8.0 which no longer includes the problematic postinstall script. Does this fix the issue for you?
@duvallj Yep, everything works perfectly fine now. Thank you, great work!
Problem description:
Installation of the package results in the following error:
The build log looks as follows:
Attempted resolution steps:
Installing the
patch-package
package does not resolve the issue on my end. I believe this only happens when there are no prebuilt binaries available.Proposed solution:
I think including
patch-package
independencies
would resolve the issue. (or reconsidering whetherpatch-package
is necessary at all)System information: