browserify / browserify/factor-bundle
Errors if directory doesn't exist—browserify does not
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 397
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Not sure if this is a bug, but if I use browserify to try to write a file to a directory that doesn't yet exist, browserify will create the directory. factor-bundle, however, will throw an error. Is there any reason for the difference in behaviour between the two?
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
No files or tests are named. Reproduce writing to a nonexistent directory with factor-bundle and compare the behavior with browserify; then inspect the relevant output-path handling and existing tests to establish which behavior is intended.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100