-
Notifications
You must be signed in to change notification settings - Fork 295
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
Bug when compiling with Knex.js on windows 10 #593
Comments
same issue here |
Same here |
Same here const newKnex = makeKnex(new Dialect(config)); TypeError: Dialect is not a constructor |
Same here |
same there |
This PS - I had originally thought this was fixed as my regex work around code wasn't picking up any matches, but this is due to some minor renaming as |
@microCloudCode Can you try the 0.27.0 and report back if you still experience a problem? |
same issue on 0.27.0 |
|
This should have been fixed in this PR: vercel/webpack-asset-relocator-loader#153 |
This was bumped in https://github.com/vercel/ncc/releases/tag/0.33.4 |
We've run into a strange issue with code compilation by ncc resulting in a crashing program on Windows 10. A repo has been created that has been verified to exhibit this issue, here: https://github.com/urbdyn/ncc-bug-1
The bug results in code within Knex.js replacing string matches on imports with full paths. The repo has great amounts of detail and compiled output from a Windows and MacOS machine for comparison.
The resulting compiled code in question that seems to be resulting for this look like this on MacOS (works fine, non-buggy):
but for some reason is transformed into the following in a Windows environment:
As you can see, something very strange is occurring here which is resulting in a string comparison being replaced by the same directory path, in a hard coded manner.
I did do a bit of research on other issues in this repo and, after a bit more digging, that this seems to be a similar issue to #451.
Don't hesitate to let us know if you need any more information! Full environment details for the systems are given in the example repo.
Tagging @josh-josh-miller for visibility since he is also affected by this problem.
The text was updated successfully, but these errors were encountered: