Errors if directory doesn't exist—browserify does not

Open
#83 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
tooling

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.

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?

Dominant language
JavaScript
Stars
397
Forks
24
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from browserify/factor-bundle

All issues in browserify/factor-bundle

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.