Best practice configuration so that "npm rebuild" works?

Nobody has claimed this yet.

Hello,

In https://github.com/mapbox/node-pre-gyp#configuring an example config is shown which is adapted by many libraries that use node-gyp. We found out that this is not really working when people use "npm rebuild" on the root dir level after an nodejs upgrade in general, because this config always state "hey I'm already build and existing" even after a node.js upgrade.

After many experiments we found out that "--update-binary" as additional parameter is a ways to achieve that "npm rebuild" also updates the binary.

While discussing this in the "canvas" library" the question arised whats the "official node-pre-gyp" statement to that topic because the example is not containign this.

It would be awesome to get some opiions and insights from you as the experts :-)

More details about the current discussion we had and especially infos and effects of the alternative options like "lets user execute npm install instead of rebuild" can be found at https://github.com/Automattic/node-canvas/pull/1982

Thank you very much!

Ingo Fischer

Start with the configuring example in the linked node-pre-gyp documentation and review the node-canvas pull request 1982 for the reported npm rebuild behavior and alternatives. Done means reaching a maintainer-backed recommendation and documenting the official configuration or rebuild guidance.

Written by the indexing model from the issue text.