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

Path delimiter removed #161

Closed
stevenvachon opened this issue Nov 12, 2019 · 6 comments
Closed

Path delimiter removed #161

stevenvachon opened this issue Nov 12, 2019 · 6 comments
Labels

Comments

@stevenvachon
Copy link

  • Version: 12.13.0
  • Platform: Darwin Stevens-Mac-mini.local 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

Using c8 report and c8 mocha results in:

file: /path/to/broken-link-checker/lib/index.js error: Error: ENOENT: no such file or directory, open 'libindex.js'

Somehow, somewhere, lib/index.js is becoming libindex.js.

@bcoe bcoe added the bug label Nov 28, 2019
@bcoe
Copy link
Owner

bcoe commented Nov 28, 2019

@stevenvachon that's very odd, could you try:

npm i c8@next

There has been a bit of an overhaul to how we handle paths. If we continue to see issues, mind submitting a repo that demonstrates the issue?

@casdevs
Copy link

casdevs commented Dec 18, 2019

I'm also facing the same error using c8@6.01.

Do you use source maps?
After removing //# sourceMappingURL=... from my .js files, the error disappeared.
So it may be related to source mapping...

@casdevs
Copy link

casdevs commented Dec 18, 2019

in my case the specific problem was that I've used relative paths in the source maps I've generated.
After ensuring that source maps reference their source files by using absolute paths, the c8 errors disappeared for me.

@andrewdotn
Copy link

@bcoe Here’s a repo that demonstrates the issue:

https://github.com/andrewdotn/c8-161

It doesn’t involve c8 at all. I’m not sure if it’s a problem with babel or node, but since I see you’ve been working on source-map-support in node itself, perhaps you can suggest how to distinguish whether the issue is with babel or node?

@andrewdotn
Copy link

This is now resolved for me after upgrading to @babel/register v7.9.0 released today.

@bcoe
Copy link
Owner

bcoe commented Mar 24, 2020

👌 @stevenvachon feel free to reopen if this continues to be a problem.

@bcoe bcoe closed this as completed Mar 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants