Production bundle doesn't work
See original GitHub issueProduction invocations of react-native bundle
fail because of the transformers enabled in the production section of the .babelrc
. I managed for a while by removing the inline plugin, but now both are failing and had to remove them basically bringing my .babelrc
back to babel-preset-react-native
😢.
Have you experienced this as well, or it’s only my setup?
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
c# - Bundle not working in production - Stack Overflow
Everything works fine on my machine , but when i moved all stuff to the local web server (IIS) the css files are...
Read more >It works on development but not on production bundle. #2502
Below works good when development but not on production bundle. And not any console message indicate which parts were wrong.
Read more >Izotope Music Production Bundle 2 won't install
I thought I'd take advantage of the special pricing Izotope offered on their Music Production Bundle 2 on Halloween. I'm using a Win...
Read more >Troubleshooting build errors and crashes - Expo Documentation
Go to your build details page (find it on the build dashboard if you don't have it open already) and expand any failed...
Read more >Build for production - Lit.dev
We recommend Rollup because it's designed to work with the standard ES module format. ... The main JavaScript bundle for older browsers that...
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 FreeTop 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
Top GitHub Comments
I ran into this issue myself.
I followed this thread: https://phabricator.babeljs.io/T6946
It advised to replace “transform-react-inline-elements” with “transform-react-constant-elements”.
That worked for me @blackxored. Can’t answer why… or even if it’s going to work forever.
It’s fixed already.