Unable to resolve module './patternReg' from lib/extract/extractProps.js
See original GitHub issueI’m getting a confusing error trying to use react-native-svg on a project.
Unable to resolve "./patternReg" from "node_modules/react-native-svg/lib/extract/extractProps.js"
(this is from the expo bundler)
It seems weird since extractProps.js seems to have no mention of patternReg.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:8
Top Results From Across the Web
Issues - GitHub
Unable to resolve "./patternReg" from "node_modules/react-native-svg/lib/extract/extractProps.js" (this is from the expo bundler) It seems ...
Read more >3 - Stack Overflow
Unable to resolve "./patternReg" from "node_modules\react-native-svg\lib\extract\extractProps.js. now how to solve this problem? Thanks in ...
Read more >Error: Unable to resolve module `util` – Split Help Center
Running bundle using React Native and Javascript SDK causes an error. Bundling failed: Error: Unable to resolve module `util`.
Read more >Search - appsloveworld
Coding example for the question Unable to resolve "./patternReg" from "node_modules\react-native-svg\lib\extract\extractProps.js-React Native.
Read more >MongoDB Atlas App Services & Realm
Fresh Setup: Realm React Native Error: Unable to resolve module `./subscription` from `node_modules/realm/lib/browser/index.js` · XCode 11.3.1 ...
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
Add this to your scripts to remove extra react-native-svg packages:
When running expo, make sure to restart and clear cache (shift-r)
watchman watch-del-all && rm -fr $TMPDIR/react-* && npm start -- --reset-cache
did it for me, basically reset cache