Sadly, I always build npm packages locally with a user created for the app. Npm2nix is not usable yet afaik (I'd love to be wrong).
Last I saw, someone was proposing for it to piggyback on `npm shrinkwrap`, which I think would be the way to go for determining version numbers. Worst case, the result could be used to pre-populate an npm cache and to run npm in a sandbox for building (possibly step by step so we can store all modules separately). On Tue, Feb 2, 2016, 8:53 PM Matthew O'Gorman <m...@rldn.net> wrote: > > Yesterday I tried to package phonegap for nixos but ran into problems. > It seems several of the packages in the node-package-generated.nix no > longer exist so npm2nix over node-packages.json fails. Should this > feature be removed? If so how should I go about packaging npm software > for nix. > > -- > Matthew O'Gorman > BM-NBUmia4p88Jny5bZbRGcMt64SWWp5WVv > TorChat: 5w3dtk7nhkkijcpc > Site: https://b.rldn.net > Xim/Email: m...@rldn.net > mog@rldn:~$ fortune wisdom -s|cowsay -f /dev/null > ______________________________________ > / There is no cure for birth and death \ > | other than to enjoy the interval. | > | | > \ -- George Santayana / > -------------------------------------- > _______________________________________________ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > -- Wout. (typed on mobile, excuse terseness)
_______________________________________________ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
