Closed akash-joshi closed 8 months ago
If you bump to eslint-plugin-svelte@2.36.0-next.3
it will fix that warning as it has experimental svelte 5 support.
Not sure if we wanna set that as the default in the create-svelte template or not
We can use the -next
version for users who select Svelte 5 and keep the stable version for users on Svelte 4
Doing this is still showing the vite unmet peer warning:
└─┬ @sveltejs/vite-plugin-svelte 3.0.1 └─┬ svelte-hmr 0.15.3 └── ✕ unmet peer svelte@"^3.19.0 || ^4.0.0": found 5.0.0-next.38
Can that be safely ignored?
Describe the bug
I went through the sveltekit create command,
npm create svelte@latest
, using the sveltekit default app and installing all optional dependencies via CLI - prettier, eslint, svelte-5, etc. Aftercd
ing into the directory and runningnpm i
, anoverriding peer dependency
error pops up.Reproduction
Root app - https://github.com/akash-joshi/art/tree/173f23f3cfe208c893e2e242d9fe5aff48f3fc32
Reproduction steps:
Logs
System Info