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
Weird behavior with path.resolve
#444
Comments
This is by design - assets are emitted wherever referenced as file paths will not work out otherwise. Can you perhaps share where |
it's the same reference both times, so the difference is in variables names? :) And this is the code in question https://github.com/alexindigo/configly/blob/master/lib/load_files.js#L39-L44 Thank you. |
I tried to replicate this with the following code:
when observing the outputted source I don't see the rewriting you are referring to at all here. Can you perhaps clarify how I could replicate your case. |
@guybedford Yes, because I added workaround in the latest version, |
Ah perfect, yes I can confirm this is a bug thanks. |
Thank you @guybedford Probably don't need that "need more info" label :) |
Switched from
@zeit/ncc@^0.11.0
to@zeit/ncc@0.20.2
and observing weird behavior withpath.resolve
:js file
Run it with
./node_modules/.bin/ncc run test.js
Output:
And if I run
./node_modules/.bin/ncc build test.js
, this is what I get:Above are not full files, but lines of code in question.
Thank you.
The text was updated successfully, but these errors were encountered: