···11-# Svelte + TS + Vite
22-33-This template should help get you started developing with Svelte and TypeScript in Vite.
44-55-## Recommended IDE Setup
66-77-[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).
88-99-## Need an official Svelte framework?
1010-1111-Check out [SvelteKit](https://github.com/sveltejs/kit#readme), which is also powered by Vite. Deploy anywhere with its serverless-first approach and adapt to various platforms, with out of the box support for TypeScript, SCSS, and Less, and easily-added support for mdsvex, GraphQL, PostCSS, Tailwind CSS, and more.
1212-1313-## Technical considerations
1414-1515-**Why use this over SvelteKit?**
1616-1717-- It brings its own routing solution which might not be preferable for some users.
1818-- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
1919-2020-This template contains as little as possible to get started with Vite + TypeScript + Svelte, while taking into account the developer experience with regards to HMR and intellisense. It demonstrates capabilities on par with the other `create-vite` templates and is a good starting point for beginners dipping their toes into a Vite + Svelte project.
11+# Semble Import Studio
2122222-Should you later need the extended capabilities and extensibility provided by SvelteKit, the template has been structured similarly to SvelteKit so that it is easy to migrate.
33+Static Svelte app to stage Semble bookmark imports from a URL or pasted markdown, enrich with Citoid metadata, compare with existing Semble records, and create only new cards/collections.
2342424-**Why `global.d.ts` instead of `compilerOptions.types` inside `jsconfig.json` or `tsconfig.json`?**
55+## Local dev
2562626-Setting `compilerOptions.types` shuts out all other types not explicitly listed in the configuration. Using triple-slash references keeps the default TypeScript setting of accepting type information from the entire workspace, while also adding `svelte` and `vite/client` type information.
77+```bash
88+npm install
99+npm run dev
1010+```
27112828-**Why include `.vscode/extensions.json`?**
1212+## OAuth setup
29133030-Other templates indirectly recommend extensions via the README, but this file allows VS Code to prompt the user to install the recommended extension upon opening the project.
1414+This app uses OAuth PKCE against the ATProto authorization server (default `https://bsky.social`).
31153232-**Why enable `allowJs` in the TS template?**
1616+1. Update `public/client-metadata.json` with your deployed origin and redirect URI.
1717+2. Deploy the static build to your subdomain.
1818+3. Ensure the `Client metadata URL` and `Redirect URI` fields in the app match your deployed origin.
33193434-While `allowJs: false` would indeed prevent the use of `.js` files in the project, it does not prevent the use of JavaScript syntax in `.svelte` files. In addition, it would force `checkJs: false`, bringing the worst of both worlds: not being able to guarantee the entire codebase is TypeScript, and also having worse typechecking for the existing JavaScript. In addition, there are valid use cases in which a mixed codebase may be relevant.
2020+For example, with `https://semble.example.com`:
35213636-**Why is HMR not preserving my local component state?**
2222+- `client_id` should be `https://semble.example.com/client-metadata.json`
2323+- `redirect_uris` should include `https://semble.example.com/`
37243838-HMR state preservation comes with a number of gotchas! It has been disabled by default in both `svelte-hmr` and `@sveltejs/vite-plugin-svelte` due to its often surprising behavior. You can read the details [here](https://github.com/rixo/svelte-hmr#svelte-hmr).
2525+If the OAuth server requires additional scopes or a different authorization server base URL, change them in the UI.
39264040-If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
2727+## Source format
41284242-```ts
4343-// store.ts
4444-// An extremely simple external store
4545-import { writable } from 'svelte/store'
4646-export default writable(0)
2929+```markdown
3030+# Collection name
3131+- https://example.com : optional note
3232+- [Optional title](https://example.com)
4733```