Skip to content
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

Conflicts in svelte resolve #176

Open
DanielAlcaraz opened this issue Apr 25, 2023 · 5 comments
Open

Conflicts in svelte resolve #176

DanielAlcaraz opened this issue Apr 25, 2023 · 5 comments

Comments

@DanielAlcaraz
Copy link

Hi,

I upgraded my project dependencies and some new warnings appeared. This is the message:
[vite-plugin-svelte] WARNING: The following packages use a svelte resolve configuration in package.json that has conflicting results and is going to cause problems future.

Here there is more info about the conflicts by the vite-plugin-svelte team:
https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#conflicts-in-svelte-resolve

@development-vargamarcel

this might help (for maintaner):
isue: ItalyPaleAle/svelte-spa-router#310
fix: ItalyPaleAle/svelte-spa-router#313

@jonnitto
Copy link

Should be solved with 85fdeaf

@development-vargamarcel
Copy link

@ctibo
Copy link

ctibo commented Feb 28, 2024

I'm still getting the error with v2.2.1.
Rolling back to v2.2.0 removes the issue.

Relevant package.json info from my setup :

"@sveltejs/kit": "^1.20.4",
"svelte": "^4.2.7",
"svelte-preprocess": "^5.1.0",
"svelte-portal": "^2.2.1"
"typescript": "^5.0.0",
"vite": "^4.5.0"

The issue:

OUTPUT:
#12 28.71 2:27:47 PM [vite-plugin-svelte] WARNING: The following packages use a svelte resolve configuration in package.json that has conflicting results and is going to cause problems future.
#12 28.71
#12 28.71 [email protected]
#12 28.71
#12 28.71 Please see https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#conflicts-in-svelte-resolve for details.
[2024-Feb-28 14:27:48.181001]

@mig-hub
Copy link

mig-hub commented Mar 28, 2024

Same, I get the error with 2.2.1
Indeed it does not warn when using 2.2.0 instead

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants