Weird warning
See original GitHub issueI had to update node to 14.x, and after running npm start -- --reset-cache
I’m getting the following warning:
warn Package async-mutex has been ignored because it contains invalid configuration. Reason: Package subpath './package.json' is not defined by "exports" in app/node_modules/async-mutex/package.json
Ideas?
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
21 Stupid Warning Labels That Will Make You Feel Like a ...
From "don't pour coffee on crotch," to "don't eat iPod Shuffle," these real funny warning labels will make you wonder who's dumber: ...
Read more >In Pictures: 24 Stunningly Dumb Warning Labels - Forbes
Label: Never operate your speakerphone while driving. · Label: May cause drowsiness. · Label: Do not hold the wrong end of a chainsaw....
Read more >21 ridiculous warning labels that will make you feel like a genius
Keep reading for some warning labels so strange that you'll be left wondering why the company felt they had to even print them....
Read more >Silly Warning Labels (List)
"Caution: The contents of this bottle should not be fed to fish." -- On a bottle of shampoo for dogs. ❖ "Do not...
Read more >43 Funny Warning Signs ideas - Pinterest
Feb 24, 2012 - Find even more funny warning signs at http://www.funnysigns.net/category/warning/. See more ideas about funny warning signs, funny signs, funny.
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’m sorry I didn’t quite meet my schedule. I’ve released a fix with 0.2.3
Cheers -Christian
OK, I just checked and can reproduce the warning by adding
async-mutex
to a react-native project. This seems to be an issue with react-native; a relevant upstream report is https://github.com/facebook/react-native/issues/28710 . I’ll release a workaround later this week.