Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

jitsu has a large dependency tree #217

Open
Marak opened this Issue Apr 6, 2012 · 2 comments

Comments

Projects
None yet
3 participants
Contributor

Marak commented Apr 6, 2012

While it's a good thing that we have many many small modules that have distinct units of functionality, this does mean a lot of round-trips back and forth to npm while jitsu is installing.

Some investigation is required, but I'd like to reduce the amount of round-trip HTTP requests that are made to npm registry in order for jitsu to install.

I suggest using one of npm's bundling commands, or perhaps just vendoring the all deps into the .node_modules folder for releases. Whatever we choose, it should be the choice that will require the least amount of total installation time and possibilities for failure.

Owner

indexzero commented Jul 10, 2012

+1 We can bundle all our dependencies

Contributor

jfhbrook commented Sep 25, 2012

This seems like a reasonable thing to do. I'll investigate adding this in time for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment