When it comes to publishing your packages on npm, what do you ship? Lowest-common-denominator ES5? ES2017? Something in between? Multiple variants?
-
-
We're targeting Node 6 since that's still LTS. I'd love to discover a way to publish a package which can target different versions.
-
Engines

-
But I can only have 1 "latest" tag? I guess that was my worry. Folks will install latest, get a warning that the engine doesn't match, and have to find what the last version to support 6 was? That's not fun.
-
Oooh, so what you’re talking about is multiple versions? You’re right about latest, but you could theoretically do 1.3.2-es6 and 1.3.2-es2018 Definitely seems like an interesting problem that could be solved on the
@nomjs side
-
-
omg it does!
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.