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.
Breaking changes in this project
See original GitHub issue👋 After upgrading from v 2.2.3 to v2.3.3 (the versions in between are not published on NPM), generators stopped being transpiled.
I would consider this to be a breaking change (e.g. if the resulting code after upgrading from 2.2.3 to 2.3.3 is passed to uglify, it will throw errors, IE11 will throw because it doesn’t understand generators, etc). The issue is present in 2.4.0 too.
It would be useful to consumers if you could clarify what you consider to be breaking changes for this project so people know what semver ranges are safe to use (e.g. ^2.0.0 vs ~2.2.0 or 2.2.3)
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
v2.2.3 wasn’t supposed to transpile generators which the docs state here.
Usually I’m on the side you’re advocating for, to be honest - but in this case, our babel preset is meant to be paired with our eslint config and style guide, which strictly bans generators.