SvelteToast is not a valid SSR component
See original GitHub issueI’m getting this error with sveltekit ssr
<SvelteToast>
is not a valid SSR component. You may need to review your build config to ensure that dependencies are compiled, rather than imported as pre-compiled modules.
Issue Analytics
- State:
- Created 10 months ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Sveltekit integration: is not a valid SSR component · Issue #595
Juts started new project with Sveltekit, then installed Carbon components with npm i -D carbon-components-svelte --save Then started to code ...
Read more >r/sveltejs - Reddit
I ran into this error in my SvelteKit project. is not a valid SSR component. You may need to review your build config…...
Read more >Svelte FAQs - GitHub Pages
Getting a lot of “…is not a valid SSR component” 500 errors in SvelteKit. SSR, or server-side rendering, is the process of running...
Read more >External Dependencies not working in Nav.svelte
I am trying to load sv-bootstrap-dropdown module in nav.svelte component but I am getting the error <Dropdown> is not a valid SSR component....
Read more >Svelte Radio - Transistor.fm
Swyx: Svelte will stay on top of React; Antony: Mastodon is not the answer ... it manually is a very good a very...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It’s likely due to the deprecation of
svelte
field that landed in SvelteKit a few days ago. Looks like I’ll have to split the package into two - one for Svelte, and one for vanilla JS.As a matter of priority, SvelteKit consumers of this package should install the latest RC with the
@next
tag:This stop-gap release migrates the existing stable codebase
v0.8.2
as-is tosvelte-package
, which then SvelteKit will be able to correctly pick out; otherwise, the compiled code is used instead, and that’s a bad thing.This buys us some time while I migrate the tests, update the demo, refactor the codebase, and add some new stuff for
v1
.