forever broken again with nconf 0.5.0

[qzaidi]

with nconf 0.5.0, its broken again for me in the last 2 days. can we update package.json to use 0.4.x?

[FGRibreau]

+1
Please be more precise with package.json dependency's version.

[Leonya]

+1, please fix this.

[AvianFlu]

We'll publish a fix with an 0.4.x minor version lock to npm as soon as possible, but can any of you describe the errors? Moving forward, it's better to add compatibility than to just freeze the version for good.

[Leonya]

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: undefined is not a function
at Object. (/usr/local/lib/node_modules/forever/lib/forever.js:45:23)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)
at Module.load (module.js:351:31)
at Function._load (module.js:310:12)
at Module.require (module.js:357:17)
at require (module.js:368:17)
at Object. (/usr/local/lib/node_modules/forever/bin/forever:7:15)
at Module._compile (module.js:432:26)
at Object..js (module.js:450:10)

[mmalecki]

I'm reopening this as a remainder of porting forever to nconf@0.5.

[rubycut]

I can see it commited, but it's not pushed to npm, still can't install 0.7.4.

[Marak]

Can't publish until later today.

Publishing to NPM isn't a prerequisite for using the library. You can still just clone the repo and npm link it.

[indexzero]

published.