npm 3.0

[mikefrey]

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

[hefangshi]

so, any plan or solution with this? It seems even use npm 3.0's new node_modules directory, it's still valuable to use pac.

[mikefrey]

I'm not sure how to tackle it just yet. Currently, pac ignores any installed modules that are not explicitly included in the package.json file. I see a couple of options:

1. Just pac all modules found in the node_modules directory and ignore package.json
2. Build a dependency tree in memory (perhaps npm can be used for this) and pac any modules found in the node_modules directory that exist in that tree.

I'm leaning towards option 2, but haven't had time to explore it.

[d-werner]

Many thanks for sharing pac! I'm considering to integrate it in our build process.
But just to be sure ... are you definitely going to adapt pac for npm 3.x? ;-)

[tomcrabb]

Hey Mike, any plans to support NPM 3 yet? Keen to start using it for our builds :)

[Josh-a-e]

@tomcrabb if you're interested we just use a rudimentary script

tar cvJf node_modules.tar.xz node_modules

for preparing our node dependencies, then in our Dockerfile (or wherever)

RUN tar xvJf ./node_modules.tar.xz
RUN rm node_modules.tar.xz
RUN npm rebuild

It's obviously a lot cruder than node-pac here, but it certainly works well

[tomcrabb]

@Josh-a-e thanks, we've implemented something similar now.

[twalling]

You could also use the legacy-bundling flag in your .npmrc file or during npm install --legacy-bundling and I believe pac would still work.

[VanDavv]

@mikefrey do You plan to develop further Your package to handle npm@3.x.x ?