Still alive #37

Open
ghost opened this Issue May 10, 2012 · 7 comments

3 participants

@ghost

Did you replace this in your workflow with something better?

@tj
Owner
tj commented May 10, 2012

not yet but I have something in the works

@jgallen23

can we get a sneak peek?

@athibaud

@visionmedia I know node 0.8 is just around the corner but would you mind updating the npm package so it works with node 0.6.x?

@ghost
@athibaud

@rumplefraggle sorry, I don't mean it' doesn't work with node 0.6.x, just that I use node 0.6.x and want to be able to install it via npm but the package.json file has: "engines": { "node": "0.4.x" } which prevents we from installing it that way.
I understand I could fork and just modify that line to "engines": { "node": "0.6.x" } or "node": ">= 0.4.x" and have my package.json fetch asset from my fork but I didn't think it was a strong enough case for forking...
If you have a better solution please tell me.

@ghost
@tj
Owner
tj commented Aug 6, 2012

I'm building something better but it's a similar idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment