node@9 9.11.1

[jasonseminara]

• Have you followed the guidelines for contributing?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install <formula>)?

---

[ryenus]

Too bad this wasn't part of the node 10 formulae update

[ilovezfs]

Thanks for the suggestion @jasonseminara. However, we only add node@* versioned formulae for the LTS releases, which is not the case here.

[ryenus]

Here is a reason for this:

So anyone using yarn in Node.js 10 and any of webpack's +8.6k dependents would encounter this issue.

[ilovezfs]

@ryenus I don't follow. Use node@8, no?

[ryenus]

maybe yes, but if one was previously using node v9, having an option to reinstall the same version, is probably the best.

[chrmoritz]

Assuming you didn't removed node 9.11.1 from the Cellar yet, you could just go back with brew switch node 9.11.1.
Node 9 is currently in maitance only and will only receive an update again, if there will be a security update released until End of June, when it will finally become EOL.
That being said, a versioned formula does make more sense if the release line is still actively worked one, which is not the case for node@9.

And regarding the issue with incorrect engines ranges in upath: You could just set ignore-engines to true in your yarn config to stop yarn from erroring out on unmatched engine ranges (in npm it would be only a warning btw).

[anodynos]

Hello everyone - I merged anodynos/upath#15 & published it - thanks & sorry for the delay! You remove the ignore-engines workaround.

[ilovezfs]

Thanks @anodynos!