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.
Babel 7 present env using useBuiltIns: usage does not transpile AMD 'define' properly
See original GitHub issueBug Report
Current Behavior Using babel 7 with present env with configuration “useBuiltIns: usage” then any amd modules that contain an instance method that needs to be polyfilled will not transpile correctly.
Modules that do NOT contain instance methods will transpile correctly.
When executing the broken module you will get:
Uncaught ReferenceError: define is not defined
Input Code I have set up a dummy project with minimum configuration to demonstrate the bug: https://github.com/chaoyzeng/babel-7-present-env-bug
just run the webpack dev server and load the webpage to see the console error.
Expected behavior/code All amd modules are treated the same regardless of the code that they contain.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
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
Is there an existing feature request for supporting AMD?
Even if Babel properly injected AMD dependencies for polyfills,
core-jsdoesn’t provide AMD or UMD sources so it cannot work anyway.Unfortunately, you have to either load
core-js(or another polyfill) with a<script>tag or use a bundler such as Webpack.