I have an existing package that has a new version with a dependency on
lodash-node so I was trying to package it but ran into the question of
exactly what it is and how to deal with it...
We have lodash packaged already and as bast I can figure out lodash-node
is the result of using lodash-cli to build node modules from lodash.
Though I'm not sure what that means when lodash is already a node module?!?
In any case does that mean I should package lodash-cli first and then
make the lodash-node package do that build step?
Tom Hughes (tom(a)compton.nu)
For rawhide I've been trying to keep my nodejs packages up to the latest
releases as much as possible. This isn't really that hard because of
the wonderful rpm macro's, and the general consistency of npm packages.
But nodejs-nan is making me change my habbit.
Since May 6 (less than 30 days ago), there has been
nan 1.0.0 (which broke the ~0.8 dependencies)
nan 1.1.0 (which broke the ~1.0 dependencies)
nan 1.2.0 (which broke the ~1.1 dependencies)
I have a few packages that currently depend on ~1.0. In the past they
generally updated a few days after nan updated. None of them have this
I wouldn't be worried if they were doing ^1.0, but they aren't yet.
Anyway, my plan is to wait until at least one of my packages that depend
on nan updates to be able to use the latest nan versions. Then I'll
update nan to whatever version that happens to be that day.
Anyone have any better ideas?