Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Plans to drop babel in v3

See original GitHub issue

I have been thinking about this lately, once we dropped node v4 and v6 support in 3.x release, do we still need babel?

My gut feeling is node v8+ are modern enough that all of our code are covered, so there is no value in transpiling (and I want to change back to CommonJS syntax)

https://node.green

If possible I want to drop our build step (rollup) altogether.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:9 (1 by maintainers)

Top GitHub Comments

1reaction

bitinncommented, Jun 12, 2019

@TimothyGu I hear you, but the status quo seems to be that many bundling tools are better at transforming from CommonJS to ESM? We have had a lot of problem with people trying to package up node-fetch for AWS using Webpack.

(My guess is most of them are confused about how Webpack/ESM work, but my anecdote observation remains that Webpack seem to just work with CommonJS?)

I love the named export from ESM, for sure, just that it seems to cause some troubles for users at the moment.

0reactions

Richienbcommented, Sep 8, 2019

Babel and rollup have been dropped in favour of microbundle in 3.x