iojs v1.0.3 (new formula)

[DomT4]

Alternative implementation of #35853 for discussion/giggles/etc.

[DomT4]

On this line: If you follow that line, you can just do npm install -g blah or similar. We could simplify this, but I wanted to give maintainers and people options for discussion for now, and I wanted to give developers a way to activate the iojs npm without having it absolutely conflict with the Node npm. This reasonably-hideous workaround achieves that.

[DomT4]

Further discussion: Yes, for now, I've removed the option to not install npm. Honestly, not installing npm in this particular format & formula is a complete pain in the neck, and the scripts become much less useful without npm around. I'll put it back if there's strong demand for the option from the maintainers or well, anyone really, but at least for testing purposes I think mandating it isn't the most awful thing we could do.

[tdsmith]

Can you summarize the major points of difference with the existing PR?

[DomT4]

Sure.

1. The npm option has been cut. It's mandatory. Reasoning is in the post above.

2. This formula installs iojs and npm into libexec and then moves npm into homebrew_prefix/share/iojs/lib/node_modules and creates exec scripts for npm and iojs into the main homebrew_prefix/bin. This allows it to not conflict with Node whilst being more readily usable and accessible than keg_only or a solid conflicts_with does.

The exec scripts are the kinda nifty part to play with here - the iojs exec script triggers an instruction to iojs so it knows where the node_modules for it are located, and the npm-iojs exec script triggers a temporary jiggle to the $PATH so npm can always find the node symlink from iojs.

3. The new iojs/npm_modules bin becomes where npm executables are placed, and the overly lengthy caveat that we'd need to trim over time explains how to access those. What we could do, over a longer-term, is write two short bash scripts that would allow users to do gonode or goiojs and it would switch the node symlink and node_path over automatically. This wouldn't be difficult, but it's not without risk, so I considered a smaller step a better way to get there.

4. As alluded to above, npm install -g example installs example into HOMEBREW_PREFIX/share/iojs/lib/node_modules and symlinks that to HOMEBREW_PREFIX/share/iojs/bin.

[DomT4]

On another small note: I know @othiym23 wanted to avoid renaming npm away to something else, and this is a compromise of that. The exec script placed in homebrew_prefix/bin is called npm-iojs but it is really just a glorified symlink for all intents and purposes - It's also something you can easily negate having to use by prepending the $PATH as discussed in the caveats. If you prepend the $PATH you can just do npm install -g example and that would work.

[xu-cheng]

cb5ace6

[DomT4]

Nice spot! Will fix as soon as my internet decides it wants to go a little faster than 7KB/s 😿

[MikeMcQuaid]

Let's make this without-completion

[DomT4]

I didn't know if that was too clashing against Node, given this deliberately removes the conflict and keg mechanism? (As an experiment. Not saying this is the best way to get it done, just an alternative to the other discussion). I suppose I could do a little if file already exists don't replace it detection dance? Although that could prove troublesome at updates.

[DomT4]

Incredibly useful upstream list monitoring what's broken in terms of packages and when they are fixed here. Thanks to @timoxley for setting that up.

[DomT4]

Per Mike's comment in the other thread, closing this PR 👍