Open JounQin opened 8 months ago
Latest commit: fef79627e925c3f8d98941114bbb41dc36c3f2e8
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
76:5 error "postcss-load-config@^5.0.2" is not compatible with "node@^14.17.0||>=16.0.0". Allowed is: "node@>=18.0.0" node-dependencies/compat-engines
81:5 error "synckit@^0.9.0" is not compatible with "node@^14.17.0||>=16.0.0". Allowed is: "node@^14.18.0||>=16.0.0" node-dependencies/compat-engines
Do we want to release a major version for this?
I believe we should match svelte
itself.
Thank you for the PR. I would like to release eslint-plugin-svelte v2.36 after the stable version of svelte v5 is released, and then work on the next major version.
Even if Svelte 5 is released, I don't think we can drop Node < 18 as long as we continue to support Svelte 4 and Svelte 3. I think it is a good idea to support only Svelte 5 in the next major version.
I meant this PR should target on the next major version.
The main
itself is targeting Svelte v5, how can I create a PR for old releases?
cc @ota-meshi
There is currently no way to manage multiple versions in this repository 😓
It needs multiple branches. For example https://github.com/mdx-js/eslint-mdx/tree/release-v2.
close #636