How to deal with multiple target?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
I currently have an electron project so that I should have electron as the target.
But I also have some native-module which will be use with node (for web pack -, have node-sass)
How to deal with those different targets with node-pre-gyp?
Contributor guide
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 reviewing node-pre-gyp's documentation and configuration for Electron projects, native modules, webpack, and node-sass. Determine whether the project supports separate Node and Electron targets and document a confirmed setup; done means users can follow the guidance for both targets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, node.js
- Domain
- build-system, desktop, tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100