Weird warning

[cristianoccazinsp]

I 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?

[DirtyHairy]

Hi @cristianoccazinsp ,

I cannot reproduce your issue by simply importing async-mutex in Node 14. Can you explain what exactly npm start is doing in your project, or do you maybe have a link to your repository?

Cheers
-Christian

[cristianoccazinsp]

Hello, It's a react native project. However, I ended up reverting to node 12 since it was causing various other issues and the warning went away. El sáb., 9 de mayo de 2020 16:57, Christian Speckner < [email protected]> escribió:

…

Hi @cristianoccazinsp <https://github.com/cristianoccazinsp> , I cannot reproduce your issue by simply importing async-mutex in Node 14. Can you explain what exactly npm start is doing in your project, or do you maybe have a link to your repository? Cheers -Christian — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALU263H3N5OCLRAWF4UVKBTRQWYSFANCNFSM4M4HCADQ> .

[DirtyHairy]

Hi @cristianoccazinsp ,

Glad to know that your issue is solved. However, if there is an issue with async-mutex in combination with Node 14, I would very much like to resolve it it --- is the affected project publicly available so that I can try to diagnose the issue?

Cheers
-Christian

[cristianoccazinsp]

It's not publicly available, but any react native project with that module as a requirement should trigger it. Again, only with node 14 for some reason. Perhaps there was something cached, and everything seemed to work fine regardless of the warning El dom., 10 de mayo de 2020 16:53, Christian Speckner < [email protected]> escribió:

…

Hi @cristianoccazinsp <https://github.com/cristianoccazinsp> , Glad to know that your issue is solved. However, if there is an issue with async-mutex in combination with Node 14, I would very much like to resolve it it --- is the affected project publicly available so that I can try to diagnose the issue? Cheers -Christian — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#14 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALU263AFLVPKPZ4IXKP2QQ3RQ4A4NANCNFSM4M4HCADQ> .

[macfanatic]

I'm seeing this warning at boot in my react native (expo managed sdk 37) project on node v13.12.0

[DirtyHairy]

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 facebook/react-native#28710 . I'll release a workaround later this week.

[DirtyHairy]

I'm sorry I didn't quite meet my schedule. I've released a fix with 0.2.3

Cheers
-Christian