Skip to content

Conversation

@mastef
Copy link

@mastef mastef commented Jul 23, 2018

Currently if source files are referred to with a file:// path, path.resolve will create an invalid path :
file:///folder/filename.js will turn into /current/directory/file:/folder/filename.js and then the script cannot load the content.

By using url.parse, we'll get the correct path : /folder/filename.js

mastef added 7 commits July 23, 2018 15:02
Currently if source files are referred to with a `file://` path, `path.resolve` will create an invalid path :
`file:///folder/filename.js` will turn into `/current/directory/file:/folder/filename.js` and then the script cannot load the content.

By using `url.parse`, we'll get the correct path : `/folder/filename.js`
Applied resolveProtocol() to source filenames, and sourceRoot paths as well, as they get resolved incorrectly before new Node is instantiated.
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

Successfully merging this pull request may close these issues.

1 participant