Switch to SvelteKit/Svelte-library style project setup / publishing

[vatro]

I've been struggling with project setup issues ever since, especially the correct TypeScript setup. Currently, I'm pretty annoyed by some strange / inconsistent TS behavior inside the svelthree-project vs. svelthree-package installed in newest SvelteKit-app, so I've decided to take a deeper look at threlte which is using a SvelteKit-setup.

I've replaced threlte source with svelthree source etc., but was not able to npm i inside threlte/packages folder, getting the config.kit.package has been removed — use @sveltejs/package instead error. I then tried a fresh SvelteKit-app install and have noticed the Library-option while running npm create svelte@latest my-app.

There's a link inside the fresh SvelteKit-library-project to: https://github.com/sveltejs/kit/tree/master/packages/kit

It seems that switching to SvelteKit-setup is the way to go, so let's give it a try!

[vatro]

Oh, yeah, so far so good! 🥳 Finally I see light concerning a decent project setup with proper TS + ESLint etc. It's going to be much more fun developing + code quality will massively improve (after fixing all ESLint issues). 🚀

[vatro]

IMPORTANT notices:

• @sveltejs/package's type definitions generator (emitTypes: true) doesn't like export function foo or export async function foo: generates get undefined() and set undefined(). Those need to be rewritten to export const foo = () => {...} or export const foo = async () => {...}

• @sveltejs/package's type definitions generator (emitTypes: true) creates types by adding Props to the component's class name, so they interfere with svelthrees *Props types. Those need to be changed to *Properties.

• @sveltejs/package's type definitions generator doesn't allow importing and usage of three.js classes with the same name as the component itself. Currently we're just doing import { Foo } from 'three' inside Svelte components, which works (no errors), but will produce an "incomplete" d.ts file with an empty __propDef ( declare const __propDef: any; ) so all component props will be typed as any. Atm, I don't know if type definitions generation can somehow be tweaked in order for this to work.

  Solution is to import { Foo as FooDifferent } from 'three'.
  threlte also does it this way, e.g.: import { Foo as FooThree } from 'three'.

[vatro]

done 🥳
see 2500169