-
-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package manager issue #42
Comments
@ahmadbakhshi Which package manager are you using? There should only be a |
I prefer to use pnpm. OS: mac These are my stpes
Error: [Reanimated] Invalid value passed to This error is located at: If I use the existing package-lock.json and npm, it works. |
@ahmadbakhshi With pnpm and expo, if I remember correctly you might have to add a Can you try that out and see if it works? Reference: an expo repo that uses pnpm |
@ahmadbakhshi you may also need to follow the steps further down in the readme related to peer dependencies in the afforementioned byCedric monorepo as well: I also want to point out there's an open issue in expo related to explaining pnpm compatibility. Of note this comment:
(this comment is by the same author as the aforementioned pnpm monorepo) and
In other words, this project probably isn't specifically responsible for pnpm not working. You'll likely need to implement workarounds and it is apparently currently not officially supported by expo yet due to pnpm's isolated modules approach I will also add that the specific error you're seeing is being emitted by the dependency react-native-reanimated; Of note, there's a few issues related to using |
I already mentioned that I have added |
I have gone through the entire It should be related to the lock file. |
@ahmadbakhshi , I did a package-lock regeneration 2 days ago here: #41 and smoke-tested every component with npm. I could verify that one works. Do you see differences between the lock file you just created and the one in that PR? More importantly, can you reproduce the error using the lock file in that PR? If not, then the break could be in a ranged dependency change in the last 24 hours or so. This might help: I am also running more up-to-date dependencies than this in another project (with npm) and things are working there as well, specifically these core versions. Note that I am not using ranged dependencies, I'm using these exact versions:
|
I updated |
@mrzachnugent I looked into this. was able to verify that regenerating the I'm looking into it right now |
@ahmadbakhshi I am surprised because I just tested this yesterday at v4.0.23 on #41 which probably needs to have some other dep locked. If you regenerate the lockfile with the declared version range it will install 4.0.23 since its preceded with I was also able to get this to run with .pnpm and it was necessary to add the .npmrc file with Can you try again after removing the ^ from nativewind and locking to |
@mrzachnugent I've opened a PR that I believe will resolve this issue if anyone reinstalls and deletes the package-lock.json |
It worked for me. |
I've also logged a separate issue in the downstream dependency : nativewind/nativewind#785 |
Here's a related issue in nativewind related to versions higher than 4.0.13 and pnpm |
I have also tested with pnpm and this configuration and I can confirm it's working |
Why can't I use any package manager other than npm?
Even if I regenerate the package-lock.json, I get tons of errors. It only works with the existing lock file and npm
The text was updated successfully, but these errors were encountered: