The README suggests that the npm pack approach is almost a great feature, but I disagree.
npm pack, or anything that uses fstream-npm is bad to rely on when dealing with a NodeJS project. Not only does it rely on .npmignore, a file we already have a different purpose for, it also ignores tons of files we might want to keep (our main issue are private modules). In fact, the ignore semantics are incredibly complicated.
This means that the bundles created from strider-ssh-deploy are not usable application snapshots. The result of which is that we have to manually create packages, put them into HTTP-accessible storage and download them on the production server all via custom scripts.
I would propose that a simply tar czf package.tgz * is used in place of npmd-pack.
The README suggests that the
npm packapproach is almost a great feature, but I disagree.npm pack, or anything that usesfstream-npmis bad to rely on when dealing with a NodeJS project. Not only does it rely on.npmignore, a file we already have a different purpose for, it also ignores tons of files we might want to keep (our main issue are private modules). In fact, the ignore semantics are incredibly complicated.This means that the bundles created from
strider-ssh-deployare not usable application snapshots. The result of which is that we have to manually create packages, put them into HTTP-accessible storage and download them on the production server all via custom scripts.I would propose that a simply
tar czf package.tgz *is used in place ofnpmd-pack.