The library captures --dir argv parameter
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 271
- Avg merge
- 23h 40m
- Merged PRs (30d)
- 2
Description
I have a Node script which uses `--dir` command line argument for its own purposes. The script uses bcrypt, and brcypt uses @mapbox/node-pre-gyp. So long story short, when running `node my-script.js --dir=abc`, @mapbox/node-pre-gyp starts failing saying something like "can't open the file .../abc.../..." when dealing with bcrypt binary file. I think the library uses process.argv somewhere and treats `--dir` flag from there somehow.
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
Reproduce the report with my-script.js and `node my-script.js --dir=abc`, then inspect the library's process.argv handling and the @mapbox/node-pre-gyp entry point. No repository file or test is named in the issue; done means application-owned `--dir` arguments no longer change binary lookup or cause the bcrypt load to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100