-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
The Windows packager launcher script does not pass all arguments #13445
Comments
… all arguments; included packagerLauncher spec
I'm working on a pull request to fix this. |
… all arguments; included packagerLauncher spec
… all arguments; included packagerLauncher spec
…ss all arguments to the cli
…ss all arguments to the cli
Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally! If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:
If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution. |
Description
I'm hooking into the packager script and on Windows the script does not pass all the arguments, as the non-windows script does.
Reproduction Steps and Sample Code
If you execute the
packager/launchPackager.bat
with arguments, those arguments are not passed along the the underlaying node process (cli.js)Solution
This line in the
packager/launchPackager.bat
scriptnode "%~dp0..\local-cli\cli.js" start
needs to become this:
node "%~dp0..\local-cli\cli.js" start %*
That's all.
Additional Information
The text was updated successfully, but these errors were encountered: