-
Notifications
You must be signed in to change notification settings - Fork 4
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
release v5.1.2 to loosen node version restriction #201
Comments
Is there any chance you can upgrade to v6? |
not directly, as this is a transitive dependency 🤷♂️ |
are we talking about |
yes |
Sorry, I am not following, yet. So we can't upgrade it there, because...?
Reason I am asking is that I'd prefer consumers to get to 6.x rather than
staying on 5.x assuming compatibility with latest node versions.
…On Sun, 20 Nov 2022, 16:32 Michael Kriese, ***@***.***> wrote:
yes
—
Reply to this email directly, view it on GitHub
<#201 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABN5BU3YRUH6TM44WGYLL3WJI773ANCNFSM6AAAAAASDRDSIQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
i understand, but it seems madge isn't merging the update PR. maybe there's no maintainer. 😕 |
PR is open since 4 month 😕 |
I just published 5.1.3, hope that helps! |
Currently the version v5.1.1 don't allow node v18, so install fails on that node version.
So please release a bugfix with will allow any node version >= 16.0.0
It's already fixed on v5.x branch:
node-detective-postcss/package.json
Line 13 in 2a87325
The text was updated successfully, but these errors were encountered: