Skip to content
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

Closed
idancali opened this issue Apr 11, 2017 · 2 comments
Closed

The Windows packager launcher script does not pass all arguments #13445

idancali opened this issue Apr 11, 2017 · 2 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@idancali
Copy link

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 thepackager/launchPackager.bat script

node "%~dp0..\local-cli\cli.js" start

needs to become this:

node "%~dp0..\local-cli\cli.js" start %*

That's all.

Additional Information

  • React Native version: [0.43.3]
  • Platform: [both]
  • Development Operating System: [Windows]
  • Dev tools: [not applicable]
idancali added a commit to idancali/react-native that referenced this issue Apr 11, 2017
… all arguments; included packagerLauncher spec
@idancali
Copy link
Author

I'm working on a pull request to fix this.

idancali added a commit to idancali/react-native that referenced this issue Apr 11, 2017
… all arguments; included packagerLauncher spec
idancali added a commit to idancali/react-native that referenced this issue Apr 11, 2017
… all arguments; included packagerLauncher spec
idancali added a commit to idancali/react-native that referenced this issue Apr 11, 2017
idancali added a commit to idancali/react-native that referenced this issue Apr 13, 2017
@hramos
Copy link
Contributor

hramos commented Jul 25, 2017

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:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

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.

@hramos hramos added the Icebox label Jul 25, 2017
@hramos hramos closed this as completed Jul 25, 2017
@facebook facebook locked as resolved and limited conversation to collaborators Jul 25, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

3 participants