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

Missing Exports Condition Warning in Sveltekit #161

Open
fractalmandala opened this issue Mar 3, 2024 · 5 comments
Open

Missing Exports Condition Warning in Sveltekit #161

fractalmandala opened this issue Mar 3, 2024 · 5 comments

Comments

@fractalmandala
Copy link

Using this library in Sveltekit is showing a missing exports condition warning:

The following packages have a svelte field in their package.json but no exports condition for svelte.
[email protected]
Please see https://github.com/sveltejs/vite-plugin-svelte/blob/main/docs/faq.md#missing-exports-condition for details.

At the link:

If you see a warning logged for this when using a Svelte library, please tell the library maintainers.

Using the svelte field in package.json to point at .svelte source files is deprecated and you must use a svelte export condition. vite-plugin-svelte 3 still resolves it as a fallback, but in a future major release this is going to be removed and without exports condition resolving the library is going to fail.

Example:

// package.json
  "files": ["dist"],
  "svelte": "dist/index.js",
+ "exports": {
+   ".": {
+     "svelte": "./dist/index.js"
+   }
  }
@darkwiz666
Copy link

darkwiz666 commented Mar 13, 2024

#158

Looks like it's waiting to be merged or whatever.


And it's not likely to be done any time soon, so if you can, best to fork it and manage it yourself.

@jalamprea
Copy link

It looks like the PR was deleted for no reason :(
This should be pretty important because this package will not be able to continue working on future versions of vite

@MarcGodard
Copy link

I saw this too. Is this project not maintained anymore?

@mitjakukovec
Copy link

@vadimkorr
When can we expect this to be fixed and released? Thanks!

@vivian-excomweb
Copy link

@vadimkorr bumping this issue

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

6 participants