Timeline for Should published npm packages target ES5 syntax?
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 2, 2020 at 13:16 | comment | added | Gerrit0 | @JLRishe as a package user who targets ES2018, I definitely prefer packages which do not target old versions. They unnecessarily bloat my bundle. | |
| Oct 2, 2020 at 11:14 | comment | added | JLRishe | Thank you for your answer, but this is a bit beside the point that I'm getting at. What I'm really looking to know is - presuming that a given package is ES5-compatible once it is transpiled - is it customary for the package maintainer to do that transpilation and publish the result to npm? Up until yesterday, I thought that it was up to the package consumer's build process to take care of that part, but I now suspect that is not the case. | |
| Oct 2, 2020 at 7:01 | history | answered | Jörg W Mittag | CC BY-SA 4.0 |