template VS sveltefire

This creates a basic Svelte project for us from this template. We still have to install the packages that come with the template though. We can use either yarn or npm for this but I'll use yarn.

I didn't want to use Sveltekit because I don't think I would benefit a lot from things like routing and ssr, which would end up adding unnecessary complexity. I also didn't want to use some of the Svelte templates out there because they point to a repo that is now archived in favour of Vite and/or Sveltekit. Also, since I was at it, I decided to throw in a CSS framework and ended up choosing Tailwind to complete my template, but you could ignore it and go with the svelte way of doing things if you prefer.

https://sveltestrap.js.org/ https://svelte.dev/ https://github.com/sveltejs/template https://svelte.dev/repl/7eb8c1dd6cac414792b0edb53521ab49?version=3.20.1 https://svelte.dev/repl/4162507931ea406c9f03be1b3aed9e94?version=3.48.0

! could not fetch remote https://github.com/sveltejs/template

This. Using the svelte template as OP did, you should have a public directory by default.

Grab your favorite Svelte template. I'm a typescript+pug+stylus weirdo, but the standard Svelte-provided one is a good place to start.

I'm exactly using fireships approach but i changed the typescript code to javascript, removed types, https://github.com/codediodeio/sveltefire/blob/master/src/lib/stores.ts

I know of no tutorial, but maybe you can learn from https://github.com/codediodeio/sveltefire

Using the Javascript SDK worked right away, but didn't really fit the component driven approach of Svelte. So I sat down, inspired by sveltefire, and worked out a collection of components which feel at home in Svelte projects. This resulted in the project svelte-appwrite.