is bower-installer supported? postinstall will not run when dependencies extracted from cache

[akleiber]

Hi,

I have a package.json with a postinstall script to run bower-installer.
When I use npm-cache the postinstall script is not run and bower dependencies are missing.
I need bower-installer to move/rename some files from bower packages. So using bower is not an option.

package.json

{
  "name": "my-package",
  "private": true,
  "version": "0.1.0",
  "repository": {
    "type": "git",
    "url": "http://github.com/some/repo.git"
  },
  "dependencies": {
    "bower-installer": "git+ssh://[email protected]:rebuy-de/bower-installer.git#master"
  },
  "scripts": {
    "postinstall": "node_modules/bower-installer/bower-installer.js"
  }
}

The project is in two different folders due to some concurrency issues with our automatic and manual deployment.
So when npm-cache is run from folder 1 everything is fine. When run from folder 2 it uses the cached files, but there the bower dependencies from bower-installer are missing.

Is there a possibility to force run postinstall scripts from the package.json?
Am I doing it wrong?

[swarajban]

You're not doing it wrong, there is a problem with npm-cache. Right now, when running npm-cache install, I check to see if we have a cached version, and if we do, I simply unpack the cached dependency directories. I never run any of the pre-install or post-install scripts for node if I have a cached version. Good catch, will try to get to this issue soon

[akleiber]

nice, thx :-)

[dfreudenberger]

any updates on this?

[swarajban]

Have not had a chance to look into this yet, sorry

[sudhirbits]

@dfreudenberger, have you considered https://www.npmjs.com/package/local-npm?
I use it for my build servers on which there is a npm registry running locally using local-npm

[swarajban]

Happy to accept a PR for this, not sure if I'll get to it in a reasonable amount of time