Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

1

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.

JLRishe
– JLRishe

2020-10-02 11:14:51 +00:00
Commented Oct 2, 2020 at 11:14
2

@JLRishe as a package user who targets ES2018, I definitely prefer packages which do not target old versions. They unnecessarily bloat my bundle.

Gerrit0
– Gerrit0

2020-10-02 13:16:27 +00:00
Commented Oct 2, 2020 at 13:16

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »