[Pkg-javascript-devel] Bug#845227: generate sub modules like lodash.isplainobject
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 their correct versions in their node_modules folder and be actual package code code instead of recreations from source. This is also similar to https://docs.npmjs.com/files/package.json#bundleddependencies. - JDD -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#845227: generate sub modules like lodash.isplainobject
> 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 specify dep versions for a reason and it's not super safe to assume they'll function correctly with deps outside of those specified ranges. > When we update a dependency to latest version, we ensure all the packages depending on it continue to work by running tests Sounds kinda fragile. > The terms of the license allow me to flatten the dependencies. You're totally free to but I'm also free to discourage incorrect use of the package. BTW are these Debian packages targeting a specific Node version? -JDD -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#845227: generate sub modules like lodash.isplainobject
> 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 in ways that avoid the need for versionless dependents, by way of self contained packages. > The last comment about obstructing it shows your intolerance towards users of your library. You can try, but if it is Free Software, we'll find a way. You're free to use the software under the terms of its license. I'm also free to not agree with your approach. It's not super great. -JDD -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#845227: generate sub modules like lodash.isplainobject
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://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#845227: generate sub modules like lodash.isplainobject
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 npm with: > npm view lodash.isplainobject dist.tarball which will return: > https://registry.npmjs.org/lodash.isplainobject/-/lodash.isplainobject-4.0.6.tgz Thanks, -JDD -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel