Closed RanolP closed 4 months ago
Hello @RanolP thank you for reaching out. Here is a possible solution for the problem you are facing.
Let me know if this does the trick.
it works but seems to drop all the advantages from pnpm and use the pnpm as ye olde npm/yarn classic. aren't there alternatives to this?
I am facing the same problem.
As described here, the command is working on my local windows machine, just not in my CI pipeline.
So I'd rather just keep using it locally than setting node-linker=hoisted
, which defeats the purpose of using pnpm altogether and would also require me to apply many other configuration changes to my RN project and monorepo.
It would be great, if we could find a way to get codepush to work in a monorepo with a standard pnpm configuration!
Hello @RanolP @AlexanderWeigand, based on what I found out there are still a lot compatibility issues with pnpm and react native. Please try this approach
react-native bundle
command appcenter codepush release -a <ownerName>/<appName> -c <pathToBundle> -t <targetBinaryVersion> -d <deploymentName>
Take a look at docs for additional information. Please let me know if this solves the issue.
Closing due inactivity.
Description
We use pnpm for our rn repo since rn 0.73 stabilized symlink support. It works perfectly for our usecases but when I run
appcenter codepush
, it fails with the message below:Since pnpm generates
node_modules/.bin/react-native
executable file as bash script for their own node setup, it cannot be executed simply with node. Here's an example of pnpm-generated bin file:I think it should be executed without the node specification cuz react-native cli also did shebang very well (you can
cat node_modules/react-native/cli.js | head -n1
for check). If there's reason to put node, I'd like to suggest that read the first line of the file for shebang check and branching it to care about to execute with node or not.Repro Steps
appcenter codepush
with proper argumentsExpected behavior
It should work successfully.
Details
appcenter codepush
DEBUG="appcenter-cli:*"
before the command, for example,DEBUG="appcenter-cli:*" appcenter apps list
. Include the logs here, don't forget to omit any personal/sensitive data.