Skip to content
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

multiple versions of node #3

Open
jaredly opened this issue Sep 29, 2013 · 6 comments
Open

multiple versions of node #3

jaredly opened this issue Sep 29, 2013 · 6 comments

Comments

@jaredly
Copy link
Member

jaredly commented Sep 29, 2013

What's the best way to handle this?
Currently, n is used which downloads the version you want every build. This is annoying and adds >10 seconds to your build.

Suggestion:
strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and 0.11. Then on each build you wouldn't need to download them, just copy them to the appropriate directories.

@niallo
Copy link
Member

niallo commented Sep 29, 2013

So this is what engineer is for: https://github.com/niallo/node-engineer

Might need some updates but basically cache whatever is required install from binary with nave if not.

Sent from my iPhone

On Sep 28, 2013, at 9:40 PM, Jared Forsyth [email protected] wrote:

What's the best way to handle this?
Currently, n is used which downloads the version you want every build. This is annoying and adds >10 seconds to your build.

Suggestion:
strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and 0.11. Then on each build you wouldn't need to download them, just copy them to the appropriate directories.


Reply to this email directly or view it on GitHub.

@jaredly
Copy link
Member Author

jaredly commented Sep 29, 2013

Awesome.

On Sun, Sep 29, 2013 at 1:47 PM, niallo [email protected] wrote:

So this is what engineer is for: https://github.com/niallo/node-engineer

Might need some updates but basically cache whatever is required install
from binary with nave if not.

Sent from my iPhone

On Sep 28, 2013, at 9:40 PM, Jared Forsyth [email protected]
wrote:

What's the best way to handle this?
Currently, n is used which downloads the version you want every build.
This is annoying and adds >10 seconds to your build.

Suggestion:
strider-node have an npm postinstall hook that grabs 0.6, 0.8, 0.10, and
0.11. Then on each build you wouldn't need to download them, just copy them
to the appropriate directories.


Reply to this email directly or view it on GitHub.


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

@knownasilya
Copy link
Member

@jaredly @niallo how would we integrate node-engineer?

@jaredly
Copy link
Member Author

jaredly commented Oct 6, 2014

have it installed, and then instead of running npm install, we run engineer -f package.json -c "npm install"

@niallo
Copy link
Member

niallo commented Oct 6, 2014

yep, exactly.

On Monday, October 6, 2014, Jared Forsyth [email protected] wrote:

have it installed, and then instead of running npm install, we run engineer
-f package.json -c "npm install"


Reply to this email directly or view it on GitHub
#3 (comment)
.

Niall O'Higgins
W: http://niallohiggins.com
E: [email protected]
T: @niallohiggins

@knownasilya
Copy link
Member

What about the user select for a node version, would that still be done with n?

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

No branches or pull requests

3 participants