nodejs June 2014

nodejs@lists.fedoraproject.org

3 participants
3 discussions

lodash-node
by Tom Hughes 15 Aug '14

15 Aug '14

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 -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

3 9

Confused about the new nan package
by Troy Dawson 09 Jun '14

09 Jun '14

Hi, I could send this to just T.C., but I know there are other packages that rely on nodejs-nan, so I'm sending it to the list. After the nodejs macro updates where we can now have multiple instances of nodejs-nan installed, the packages I have that depend on nan do not recompile. It isn't a version thing, it is a Error: Cannot find module 'nan' problem.[1][2] Is there something that I need to do in my spec files to utilize (or not utilize) nan. Troy [1] https://kojipkgs.fedoraproject.org//work/tasks/657/6980657/build.log [2] https://kojipkgs.fedoraproject.org//work/tasks/5519/6975519/build.log

2 2

nodejs-nan
by Troy Dawson 09 Jun '14

09 Jun '14

Hi All, 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.1.2 nan 1.2.0 (which broke the ~1.1 dependencies) Wow! 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 time. 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? Troy

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

nodejs June 2014