SveteKit 3 Release Candidate

[PixelForm]

I have tried out the new SvelteKit 3 Release Candidate version and so far so good. Just one thing directly caught my attention: the '$lib' alias is removed and it seems the alias configuration doesn't work anymore as before in SvelteKit 2. I know we now have the fancy node.js built-in feature of subpath imports but they are not good enough. The alias option was ground breaking for me because it set the typescript types automatically PLUS I could generate any path for vite to load, kind of using it as virtual modules. This is not possible with subpath imports and they are usually defined within package.json. Since the SvelteKit config now moved to the vite config (best solution ever, by the way, I really love it!!), I would expect the alias to be configured there so all typescript types work out of the box again, (and the generated paths, e.g. based on an environment variable).

[teemingc]

Can you create an issue with a minimal reproduction that details how the alias option no longer works the same as before? It should work the same if someone adds $lib there. We kept it around to help ease migration although it’s deprecated

[PixelForm]

Well it is not really the issue that it doesn't work, but rather that the subpath imports would replace the alias configuration. I'd actually prefer the alias configuration and just move it to the vite config (in the sveltekit plugin in vite.config.ts). This way you have one central place for your application's build and dev server config which means easier configuration. Ofcourse you could read out the package.json in vite config but this would defeat the once great featur SvelteKit 2 had: automatic alias configuration and types geenration for the aliases.

[teemingc]

I can't remember the exact issues with those aliases but I think one of them was that you'd configure it and it would only work in your project and not another. Or that it ends up conflicting with a consumer's aliases.

[PixelForm]

Oh I see. That makes sense. I'll see if I can, for the time being, use the vite-tsconfig-paths npm package to fix my issue for now. Perhaps it can be added to the docs/blog why we need to transition from the $lib alias to the new #lib alias (subpath imports) for more clarity towards the users.