Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nyc merge fails on missing parent directory of output #976

Closed
quasicomputational opened this issue Jan 24, 2019 · 1 comment
Closed

nyc merge fails on missing parent directory of output #976

quasicomputational opened this issue Jan 24, 2019 · 1 comment

Comments

@quasicomputational
Copy link

Link to bug demonstration repository.

https://github.com/quasicomputational/nyc-merge-missing-parent

Expected Behavior

nyc creates the directory and writes to the named file.

Observed Behavior

  thing
    ✓ is okay


  1 passing (7ms)

----------|----------|----------|----------|----------|-------------------|
File      |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line #s |
----------|----------|----------|----------|----------|-------------------|
All files |        0 |        0 |        0 |        0 |                   |
----------|----------|----------|----------|----------|-------------------|
failed access input directory non-existent-directory/mocha.json with error:

ENOENT: no such file or directory, stat 'non-existent-directory/mocha.json'

Forensic Information

Operating System: Debian.
Environment Information: https://gist.github.com/quasicomputational/e423212b707fa2232d04b8dd7578bbf9

coreyfarrell added a commit to coreyfarrell/nyc that referenced this issue Jan 26, 2019
coreyfarrell added a commit to coreyfarrell/nyc that referenced this issue Jan 26, 2019
@coreyfarrell
Copy link
Member

FYI you're command-line is incorrect. The nyc merge command requires a positional argument <input-directory> before [output-file]. That said even using the correct arguments results in an exception if the destination is a file in a non-existent folder so I've posted a patch for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants