-
Notifications
You must be signed in to change notification settings - Fork 22
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
current @latest build's tag broken on Windows - latest points to 15.1. #70
Comments
cc @pyramation we have also been experiencing this with some students, seems like Windows builds are broken Maybe it would be good to add a minimal smoke test for installability on Windows/macOS/Linux? (eg. with a GitHub Actions workflow), and then schedule as such:
|
Good day, here is my latest error block after attempting to install the eslint update
|
@pyramation since it seems like it may still be a while before this is resolved, should the npm Currently |
I can do that, 15 is technically more maintained, but will do this for now :) |
Great, thanks! Confirmed that |
@karlhorky sure thing! I'd make sure if possible, to use 16.2.0 and pin exact versions — not sure if "latest" was used, but this can help in future |
For our own projects, we do this. It was coming up on fresh installs in new projects with students, where they ran |
The purpose of this issue is to save some time for future readers.
The default @latest build tag points to the 15.1.0 version installed through npm, which is broken for Windows because it uses (libpg-query@15.2.0).
I tried to install the package on Windows:
pnpm add -D libpg-query
But I experienced the following error:
It works when I install the exact version
libpg-query@16.2.0
.Solution:
pnpm add -D libpg-query@16.2.0
The reason is that
15.1.0
of libpg-query-node (so as the current@latest
) points to a broken libpg_query that has a missing 'Makefile.msvc' file. The issue in libpg_query was fixed in 16.2.0.The text was updated successfully, but these errors were encountered: