redstarbird / redstarbird/arrowpack
Node.JS runtime error occurs when a provided config directory does not exist
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1
- Forks
- 1
- Avg merge
- 3m
- Merged PRs (30d)
- 7
Description
When using the -c command line option to specify a specific directory containing a config file, the program will crash with a Node.JS runtime error if the specified directory does not exist.
Having the program halt is the preferred behaviour in this case as it is safer to not bundle with default settings if the user has accidentally mistyped the directory of the config file. The program should cleanly output an error here and not attempt to do any bundling steps.
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 at the command-line handling for the -c option and reproduce the failure with a config directory that does not exist. Done means the program reports a clean error, halts, and performs no bundling with default settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100