Bjorn Lu comments

Results 767 comments of


                                            Bjorn Lu

Vite plugin has missing CSS

Digging around the source code, my guess is that SvelteKit's manifest wasn't able to detect the component's CSS to inline it into the initial html response. I'm not sure where...

Using Vite alises in <style>

This is likely because svelte-preprocess tries to locate the import, but it doesn't know about alias. The SCSS never reaches Vite. There are two options: 1. Use `useVitePreprocess` in the...

Using Vite alises in <style>

No, but for `` specifically, it's recommended to do `import "./style.scss"` in JS instead as that's faster performance-wise.

extending a tsconfig in .svelte-kit/tsconfig.json

Looks like there has been some work for array support for `extends`: https://github.com/microsoft/TypeScript/pull/50403

`esbuild` causes import errors with `adapter-node`

adapter-node now uses `rollup` (#6896) which I believe solved the issue here

`esbuild` causes import errors with `adapter-node`

@sw-yx Seems like it's happening for `adapter-netlify` (which `adapter-auto` picks) which is still using esbuild. But the original cause #6372 only changes `adapter-node`, so something else might have caused it...

prerendering does not crawl imported images outside of pages

This is because assets are only generated for the client side builds (which doesn't bundle endpoints). SSR builds (which bundles endpoints) don't generate assets. To workaround this, you can specify...

get/set/hasContext doesn't work in production code outside a component

I thought this was already fixed via https://github.com/sveltejs/vite-plugin-svelte/issues/360. A workaround for now is to add this in `vite.config.js`: ``` ssr: { noExternal: ['sveltekit-flash-message'] } ```

get/set/hasContext doesn't work in production code outside a component

It should be added automatically but it's not, which sounds like a bug. I'll transfer this over to `vite-plugin-svelte` to track there onwards.