Good luck with all that.
I think the self contained route is probably better since it fits with how
things work with Node and its modules. Something like install the packages
in a clean cache using npm 2 so that they aren't maximally flat. Then tgz
up the package folder. It'll have all deps at the
> That means we have to maintain multiple copies of the same library and
that increases our effort to maintain it.
The maintenance cost is reduced since they're just bundled with the
package. You can treat each release of say gulp as a snapshot of their deps
and bundle it with them. Packages speci
> So in debian we patch grunt to use globally installed modules and tasks.
I'm OK with creating more hoops to jump through in this case. I think the
approach you've outlined is a bit wonky. There are ways to bundle deps
without flattening versions. You could package grunt, gulp, and whatever
else
It looks like you've ended up publishing all 407 individual packages as a
single package 😕
They were individual to allow folks to cherry-pick individual packages at
their desired versions for each.
- JDD
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://list
Hi All,
Thanks for your interest in the Lodash package. You all shouldn't need to
build from the source. It's better to simply use the packages as provided.
That way there's less likely to be user error, especially since you're not
familiar with the project.
You can get the packages by querying n
