Joshua Baker
Joshua Baker
Oops. The check failed because I added Elm to the package.json by mistake.
I have the same problem.
Hey @evancz, are you reviewing this pull request? I just tried using this feature and got "TODO deadEndsToString". Even a simple implementation like this one would be a huge improvement.
This caused a bug in my code. The behavior directly contradicts the documentation.
Potential alternate syntax for bindings and macros: ``` let iso-date = { 4 of digit; "-"; 2 of digit; "-"; 2 of digit; }; let twoOf x between = {...
npm default install command always runs if binding.gyp exists, and package install script is ignored
I am seeing this issue, too, using a private registry and trying to install the `sqlite3` package. The `hasInstallScript` workaround mentioned above is working for me.
npm default install command always runs if binding.gyp exists, and package install script is ignored
Apologies if this issue is not actually the same as mine. This message made me think that this bug specifically pertains to install behavior being different when using a custom...
npm default install command always runs if binding.gyp exists, and package install script is ignored
> npm does not do anything differently with scripts when using a custom registry All I know is that when I use my custom registry, the bug is seen, and...
npm default install command always runs if binding.gyp exists, and package install script is ignored
If you run that docker-compose.yml file (`docker-compose run node`) you'll see that npm fails to install one of those packages.
npm default install command always runs if binding.gyp exists, and package install script is ignored
I don't know about you, but when I remove the line that installs 1.4.0 and just directly install 1.4.1, it still fails. However, your reproduction doesn't have any trouble installing...