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.
Question: Configuring ES version that Babel outputs
See original GitHub issueI was wondering how to configure Babel in the non-ejected package.json to work with older browsers? I’m seeing compatibility issues with CasperJS with a PhantomJS backend and also IE 11. Also I have been looking at the ejected webpack configuration files, is there somewhere within these files I should look to configure the output JavaScript version?
I’m somewhat new to a lot of the JavaScript build tools, so general advice would be helpful. I’d like to be able to use the react-scripts without ejecting as much as possible.
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 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
One easy way to deal with this, is to polyfill everything if they run an old browser. Add this line inside your
<head>:Sure, it will be slower for old browsers, but as I said, this is super easy to do and has no impact on modern browsers, since the
nomoduleattribute makes the modern browser to skip that script.This code shouldn’t need Symbols, no. This is object spread (
{...stuff}), not array spread ([...stuff]). Please raise an issue with React Bootstrap.To add a Symbol polyfill alone, you can do:
assuming you ran
npm i --save core-jsbefore.