nwutils / nwutils/Web2Executable
Any way to add `nw` parameters not meant for chrome executable?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 974
- Forks
- 125
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 1
Description
I have a node-webkit app that requires a specific chrome extension. As a result, I must start it with nw --load-extension='path/to/extension' as mentioned in nw.js's documentation. Is there a way for me to add the --load-extension call to the generated script? It is important to note that this is an argument meant for node webkit, not for chromium, so I cannot put it in the chromium args parameter in the manifest.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked NW.js documentation, then locate how the generated script, manifest, and Chromium arguments are handled. Determine where NW.js-specific parameters could be represented separately from Chromium arguments. Done means the generated launcher accepts and emits --load-extension without treating it as a Chromium argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, python
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100