mikefrey/node-pac

pack your node_modules as *.tgz files for version control and easy deploys

node-pac's Issues

"pac doesn't exist" in Windows 7

Followed the instructions and ran "npm install pac -g". Then ran "pac" in my projects root directory, and I received this response:

"c:\Users\Norm\AppData\Romain\npm\node_modules\pac\bin\pac doesn't exist"

Pac install only changed modules

Hi!
Can i have option to install only new modules, not all of it?

Missing option for modules directory

In case of our project we have multiple ".modules" directories - one for each platform. What I would need is an option (--modules) to specify modules directory which pac should work with. I have a patch for this, so if this request seems reasonable, I can submit a pull request.

OSX -> Ubuntu tar issues

Dear @mikefrey,

You are amazing. This module rocks my face.

Sadly, gnu-tar and bsd-tar do not rock my face. We're using tar -zxf as a npm run-script to "unpac" our ./modules/*.tgz during our deploy.

The problem is that so many warnings are thrown by Ubuntu's gnutar about unknown headers, that it creates a lot of noise in our console during the deploy. In fact, so much memory is used to display these warnings that our socket's stderr maxBuffer is exceeded and our deployments crash.

As a quickfix, we're using the (gnu-tar only) flag --warning=no-unknown-keyword, but it this means other developers will either have to use a different npm run script (duplication, training, and maintenance overhead), OR we'll have to make the script compatible across various OSes. We'd love to dockerize, but its tough to get the runway for this.

The ideal solution, however, would be to not include the extended header keywords in the first place. Then both gnu-tar and bsd-tar could extract the files without complaining. I tried just setting an environment flag as COPYFILE_DISABLE=1, but that didn't seem to stop the headers from appearing :'(

Private/scoped modules

We've got some private scoped modules on npm. They are installed in node_modules like so

node_modules
----@orgname
--------package1
--------package2
----underscore
----other packages

pac currently fails trying to find a package.json file in the @orgname directory.

bower sub-dependencies ignored

Marionette's bower.json has dependencies for backbone, underscore, etc.
Running pac -s bower fails to include these in .modules (they are pulled by bower install)

Doesn't Work on Recent Versions of Node.js

This doesn't work on recent versions of Node.js. I get an error that says

ReferenceError: primordials is not defined

Also, why isn't there more hype around this product? This could potentially improve deploy times significantly. Is there a more modern solution people are using?

can this work on heroku?

As the title says: can this be made to work on heroku and how?

Install only packages that aren't already installed

Currently pac install seems to unpack and install all packages, regardless of whether they are already installed. I think that pac should optionally only install new or different packages, as judged by the version in the package.json.

NPM and bower conflict

I have a project that use npm for node dependencies and bower dependencies. I am trying to to pac both dependencies, but they get mixed.

I would be nice to have the dependencies in different folders, for example

.modules
   npm
   bower

I think it's related with #8

npm 3.0

npm 3.0's new flatter node_modules directory means pac will no longer work as intended.