-
Notifications
You must be signed in to change notification settings - Fork 10
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
Prettier 4.x is not compatible with old Node JS #254
Comments
Is it time to get rid of this restriction @grst @flying-sheep ? |
yeah, I guess supporting a recent version of prettier is more important than an old os... though RHEL7-based systems are still surprisingly prevalent (including both my old and new jobs's HPCs) |
Original plan was this, but I’m not sure if CENTOS 7 on a dev machine makes sense. Like, why run pre-commit on the HPC? |
Because you have a windows laptop an develop on the HPC using vscode remote extension |
Well, dev environments should be expected to be pretty up to date, as opposed to prod ones. I think if one needs to develop in a slow moving environment, they should use something like dev containers or conda envs or so. |
If I'm not mistaken, even when using conda, the GLIBC is one of the few things that is still provided by the OS (or maybe it was just the package that didn't declare the dependency properly back then...) Anyway, as mentioned above, I think it's more important to support a recent version of prettier than an old OS |
OK, then let’s unpin once prettier 4.0 is released (I really don’t like that pre-commit updates to pre-releases) |
OK, this is getting annoying. I wish there was a way to prevent pre-commit from updating to alpha versions, but it seems stable enough, and we can manually revert if we want to make a release before a prettier stable release or even beta comes up |
We originally fixed it due to #143. Unpinning nodejs fixed the issue for me.
The text was updated successfully, but these errors were encountered: