npm install removes the build dir !?

[strk]

[strk@gnash:/usr/src/node/modules/node-postgres(master-commit)] npm install

> [email protected] install /home/src/node/modules/node-postgres
> node-gyp rebuild || (exit 0)

make: Entering directory `/home/src/node/modules/node-postgres/build'
  CXX(target) Release/obj.target/binding/src/binding.o
  SOLINK_MODULE(target) Release/obj.target/binding.node
  SOLINK_MODULE(target) Release/obj.target/binding.node: Finished
  COPY Release/binding.node
make: Leaving directory `/home/src/node/modules/node-postgres/build'

> [email protected] prepublish /home/src/node/modules/node-postgres
> rm -r build || (exit 0)

Removing the "prepublish" script from package.json fixes this

[strk]

Seems to be an upstream issue: https://github.com/isaacs/npm/issues/3059

[freewil]

What is the point of running rm -r build for the prepublish script? Was it so it wasn't published to npm? If that is why, it looks like build/ is already in .npmignore

[strk]

Good point, @freewil. Sounds like a good workaround!
@brianc, need a pull request ?

[brianc]

There was a time when .npmignore did not correctly ignore directories and so I occasionally published the build dir, which broke everything when doing an install. It was probably fixed in the 2 years since I ran into the issue, but I never retested since removing the build dir is a simple fix. Is it causing issues?

[strk]

well, yes, as you can't use the native bindings after you npm install

[brianc]

dang. just read the npm issue comments. I'll test this out & fix it as needed asap.