I need to work with a specific feature-branch of iTowns (that is not in the npm registry yet).
Specifying a dependency as a github URL doesn't work for an iTowns (as a dependency of our project) because
(itowns) npm prepublish is not executed when a dependency-package gets installed. In other terms npm fetches the required commitish version of iTowns but doesn't run the npm prepublish on the retrieved sources of iTowns.
npm-git-install seems to be an effective temporary fix. Alas if you consider the following package.json file then an npm install on UDV-Core does indeed trigger npm-git install that in turn runs iTows npm prepublish but the build directory used for that build seems to be removed by npm-git.
I need to work with a specific feature-branch of iTowns (that is not in the npm registry yet).
Specifying a dependency as a github URL doesn't work for an iTowns (as a dependency of our project) because (itowns) npm prepublish is not executed when a dependency-package gets installed. In other terms npm fetches the required commitish version of iTowns but doesn't run the npm prepublish on the retrieved sources of iTowns.
This limiting design of npm (known since 2013, happens sometimes to be problematic (like for our need).
npm-git-install seems to be an effective temporary fix. Alas if you consider the following
package.json
file then annpm install
on UDV-Core does indeed triggernpm-git install
that in turn runs iTowsnpm prepublish
but the build directory used for that build seems to be removed by npm-git.The result is that npm-git happens to be of no help in our case. Maybe this is due to the fact that iTowns uses
peerDependencies
that cannot be installed automagically ?