You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before You File a Bug Report Please Confirm You Have Done The Following...
I have tried restarting my IDE and the issue persists.
I have updated to the latest version of the packages.
What version of ESLint are you using?
8.57.0
What version of eslint-plugin-svelte are you using?
2.36.0-next.12
What did you do?
bun create svelte@latest
# choose eslint, prettier, svelte5
bun install
What did you expect to happen?
Dependencies install successfully
What actually happened?
bun fails to process the composite version syntax ">=0.34.0-next.12 <1.0.0" and errors without adding any modules!
$ bun install
bun install v1.0.26 (c75e768a)
warn: incorrect peer dependency "svelte@5.0.0-next.80"
error: No version matching ">=0.34.0-next.12 <1.0.0" found for specifier "svelte-eslint-parser" (but package exists)
Link to GitHub Repo with Minimal Reproducible Example
I think it's a bug in bun. I think that version specification needs to be valid.
It is a shortcoming of the bun version support, sure. But given the problem can be fixed by merely simplifying the version number, why not do that? The 2 versions are semantically the same, so as a general rule try to use the more brutally supported style, no?
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
8.57.0
What version of
eslint-plugin-svelte
are you using?2.36.0-next.12
What did you do?
bun create svelte@latest # choose eslint, prettier, svelte5 bun install
What did you expect to happen?
Dependencies install successfully
What actually happened?
bun
fails to process the composite version syntax">=0.34.0-next.12 <1.0.0"
and errors without adding any modules!Link to GitHub Repo with Minimal Reproducible Example
https://github.com/RobinKnipe/eslint-plugin-svelte-issue
Additional comments
PR for suggested fix: #714
The text was updated successfully, but these errors were encountered: