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.
.babelrc should be removed from npm
See original GitHub issueReact Native packager doesn’t find preset airbnb. Removing .babelrc fixes it.
https://github.com/gaearon/redux-thunk/issues/43
https://github.com/facebook/react-native/issues/4062
Also applies to react-with-styles-interface-react-native.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5
Top Results From Across the Web
Fail to uninstall babel-cli with npm - node.js
Install Latest version of babel-cli npm install -g @babel/cli@latest. then run uninstall command sudo npm uninstall -g @babel/cli.
Read more >babel-plugin-remove-react-element
This Babel plugin can be used to remove every usage of a react component from code. Used with webpack , this can be...
Read more >babel-plugin-transform-remove-imports
Modular import plugin for babel for server-side rendering. Also works for cjs to delete imported CSS to avoid compilation errors.
Read more >babel-plugin-remove-comments
Start using babel-plugin-remove-comments in your project by running `npm i babel-plugin-remove-comments`. There are 6 other projects in the ...
Read more >babel-plugin-transform-react-remove-class-properties
Remove React propTypes from the production build, as they are only used in development. You can save bandwidth by removing them. Example. In....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
No, it absolutely should not be -
npm explore foo && npm install && npm testshould always work. The RNP has a flaw in that it transpiles node_modules, and the proper place for a workaround is a postinstall script in your top-level app that removes all.babelrcfiles from yournode_modules.Definitely not true - older syntax is almost always faster than newer syntax, because older syntax has had time to be optimized.