-
Notifications
You must be signed in to change notification settings - Fork 51
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
fix(run): pass cli args to nw process #156
Conversation
I am able to verify that arguments are passed to nw by creating the UserData dir in a custom location. Executing npm run demo creates it under test/fixture/user-data |
@ronny1982 ping, do you wanna test this PR? Steps to test:
|
The command-line help is incorrect # nw --help
(node:13867) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Usage: nw [options] [app]
Options:
--version <string>
--flavor <flavor>
--platform <platform>
--arch <arch>
--cacheDir <cacheDir>
-h, --help display help for command The |
If no cache directory is present, Maybe it would be more reliable to use the application path itself as base e.g., something like |
Tested locally and added feedback/findings related to command-line args processing in the comment section. |
Not sure how nw would fail in a workspace - could you give an example/repro? Btw, this is should be addressed in another PR. |
Created #157 |
Although unknown args are now accepted, there are a few issues:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Implementation looks good to me.
Functionality was not further tested/verified.
The issue was focusing on passing args to the NW.js app, which is solved by this PR. |
Fixes: #150