babel-plugin-module-resolver: Doesn't work in Production
I am using this package in my ReactNative project. It works well in simulator but when I publish app to app store, it doesn’t work. (To be more exact, only assets folder doesn’t work. Other folders work.)
jsconfig.json
{
"compilerOptions": {
"target": "ES6",
"module": "commonjs",
"allowSyntheticDefaultImports": true,
"baseUrl": "./",
"paths": {
"assets/*": ["src/assets/*"],
"components/*": ["src/components/*"],
"navigators/*": ["src/navigators/*"],
"screens/*": ["src/screens/*"],
"core/*": ["src/core/*"],
"questions/*": ["src/questions/*"],
"redux/*": ["src/redux/*"]
}
}
}
environment
"babel-plugin-module-resolver": "^4.0.0",
"react": "16.13.1",
"react-native": "0.63.0",
npm - 4.2.0
node - 10.21.0
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 11
- Comments: 19 (1 by maintainers)
@afestein It doesn’t work for me… Did you try production builds for iOS successfully?
This answer in the same stackoverflow thread worked for me: https://stackoverflow.com/a/62872851/1873778
babel.config.js->.babelrc.jsIssue not in this library, but in react-native code… Possibly this PR will solve the issue: https://github.com/facebook/react-native/pull/29477
Have same issue in Production… Guys, could you please check, we are really blocked. It happens in react-native@0.63, react-native@0.62 works fine. Looks like they have changed some mechanism for babel
I’m still seeing this issue in a 0.66 react native build. It all works correctly in dev on android and ios, as well as a production android build. But when I try to bundle for iOS in production it can’t resolve any of the aliases.
Is anyone else still seeing this? I’ve scoured and tested everyone’s previous solutions outlined through the many linked issues in this thread to no avail
have the same issue
@tleunen Could you please help with this issue? It is related to react-native@0.63.0+ versions… and this is really big blocker for all production projects with this babel plugin… Thanks a lot