8000 Any chance of having a single version compatible with 0.8 and 0.10 ? · Issue #129 · log4js-node/log4js-node · GitHub
[go: up one dir, main page]

Skip to content

Any chance of having a single version compatible with 0.8 and 0.10 ? #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
vojtajina opened this issue Apr 3, 2013 · 8 comments
Closed

Comments

@vojtajina
Copy link

Karma supports both Node 0.8 and 0.10. It depends on log4js ;-)

Because of https://github.com/isaacs/npm/issues/3305 it's very tricky to solve this problem. There's currently a hack for it (https://github.com/karma-runner/karma/blob/master/install-log4js.js). This hack however does not work when installing with sudo.

So having a single version that is compatible with both 0.8 and 0.10 would be very helpful.

@nomiddlename
Copy link
Collaborator

Yep - I thought about this when rewriting the file appender to handle the new streams API. I couldn't work out how to support both versions easily, so gave up. I'll have another look.

@nomiddlename
Copy link
Collaborator

I've tried to backport the old streams into the current appenders. Would you be able to take a look at the "node-0.8-backport" branch and tell me if it works for your needs, please? If it does, I'll push it to npm as a new version.

@dignifiedquire
Copy link
Contributor

I'm not sure about all the details, but wouldn't it be possible to just require readable-stream if the version is <= then 0.10. See here for an example.

@nomiddlename
Copy link
Collaborator

Ooh - cool. I'll take a look at that.

@vojtajina
Copy link
Author

Gareth, thanks a lot for looking into it, really appreciate it !

On Wed, Apr 10, 2013 at 5:29 PM, Gareth Jones notifications@github.comwrote:

Ooh - cool. I'll take a look at that.


Reply to this email directly or view it on GitHubhttps://github.com//issues/129#issuecomment-16210775
.

@nomiddlename
Copy link
Collaborator

Ok, log4js@0.6.3 pushed to npm. Thanks for the readable-stream suggestion, much cleaner than the half-arsed solution I came up with.

@dignifiedquire
Copy link
Contributor

@nomiddlename Thanks a lot for the quick fix!

@vojtajina
Copy link
Author

Huge thanks @nomiddlename !!!

jimschubert added a commit to jimschubert/log4js-node that referenced this issue Apr 25, 2013
* upstream/master:
  Removed the warning about node 0.10
  0.6.3
  added node 0.8 to travis config and package.json
  backporting new streams to node 0.8 for issue log4js-node#129
  0.6.2
  fixed the multiprocess tests
  fix version of node supported
  Fix node engine in package.json
  Updated for Node 0.10.x

* master:
rgaskill pushed a commit to rgaskill/karma that referenced this issue Jun 9, 2014
Since 0.6.3, log4js works on both 0.8 and 0.10 so we don't have to do this hack anymore...
log4js-node/log4js-node#129
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
0