Ben McCann

I cleaned up the error output **before**  **after** 

If you create a new library with `npx sv create` you will get the following `tsconfig.json`: ``` { "extends": "./.svelte-kit/tsconfig.json", "compilerOptions": { "allowJs": true, "checkJs": true, "esModuleInterop": true, "forceConsistentCasingInFileNames": true,...

> This would require significant changes to the monorepo. Is there any workaround you're aware of that wouldn't require adding file extensions to imports? Personally I would just go ahead...

https://github.com/threlte/threlte/pull/1634 looks perfect! Libraries should use nodenext and apps should use bundler, so you should use nodenext

I think there's a few errors here, but the biggest seems to be that Vite 6 is treating all `.json` files as being a `tsconfig.json` and then reloading the server...

The changes to the esbuild plugin have been reverted so the prior issue with tsconfck is gone. We're down to two errors now: [chromium-dev] › client.test.js:448:2 › Invalidation › server-only...

Thanks for pointing this out guys. I think it's an important issue, so added it to the SvelteKit 3 milestone to make sure we take a look at what can...

This discussion doesn't seem at all related to the issue here. We'd already agreed to implement this issue. If you need help with something else please ask on Discord. I'm...

What happens to `"use my-runtime"` during build? Will it be stripped out? Or will it be sent to the browser and the browser will ignore it if it's something it...

I started trying to look at this a couple weeks ago, but didn't have time to finish. Leaving some notes here with my thoughts... I refactored the page options so...