Open MathiasWP opened 1 year ago
I get the same issue after I updated my repo from svelte 3 to 4 when running a testing-library/svelte test in vitest on my svelte portable text components
When used in a Sveltekit project
Have you managed to overcome this issue btw?
When used in a Sveltekit project
Have you managed to overcome this issue btw?
I haven't tried since i created this issue. I forked the repo, made some changes to the codebase, and copied it over to our project.
When used in a Sveltekit project
Have you managed to overcome this issue btw?
I haven't tried since i created this issue. I forked the repo, made some changes to the codebase, and copied it over to our project.
Is it sensitive information to share or can you tell which parts were broken in the library for you?
When used in a Sveltekit project
Have you managed to overcome this issue btw?
I haven't tried since i created this issue. I forked the repo, made some changes to the codebase, and copied it over to our project.
Is it sensitive information to share or can you tell which parts were broken in the library for you?
No parts were broken, but when copying over the code our TypeScript started screaming at our editor. So i mostly fixed the TypeScript types
When used in a Sveltekit project
Have you managed to overcome this issue btw?
I haven't tried since i created this issue. I forked the repo, made some changes to the codebase, and copied it over to our project.
Is it sensitive information to share or can you tell which parts were broken in the library for you?
No parts were broken, but when copying over the code our TypeScript started screaming at our editor. So i mostly fixed the TypeScript types
Oh okay sounds good, I'll do the same then haha thank u!
i had this issue only occur when developing in a monorepo. outside the monorepo it works properly
edit:
during monorepo development adding
ssr: { noExternal: ['@portabletext/svelte'] }
to viteconfig supressed the issue for us as a workaround. hope this helps someone
I was able to solve this issue by just adding: export const ssr = false;
to my +page.server.js
file for the respective +page.svelte
file that was displaying this issue.
When used in a Sveltekit project