{"_id":"@dereiga/svelte-router","name":"@dereiga/svelte-router","dist-tags":{"latest":"0.1.0"},"versions":{"0.1.0":{"name":"@dereiga/svelte-router","version":"0.1.0","type":"module","license":"MIT","exports":{".":{"import":"./src/lib/index.ts"}},"scripts":{"dev":"vite","preview":"vite preview","check":"svelte-check --tsconfig ./tsconfig.app.json && tsc -p tsconfig.node.json"},"devDependencies":{"@sveltejs/vite-plugin-svelte":"^7.1.2","@tsconfig/svelte":"^5.0.8","@types/node":"^24.12.3","svelte":"^5.55.5","svelte-check":"^4.4.8","typescript":"~6.0.2","vite":"^8.0.12"},"peerDependencies":{"svelte":"^5.0.0"},"_id":"@dereiga/svelte-router@0.1.0","description":"This template should help get you started developing with Svelte and TypeScript in Vite.","_nodeVersion":"26.1.0","_npmVersion":"11.16.0","dist":{"integrity":"sha512-WgnPJjp/gAbxak4ins0y7ZmgVxVmMbrqir2Cgq0nkj7cTkW10H0K5mYiePVYRq61GkCriOp7IzMezbuLqFOYwQ==","shasum":"4d51e18455e249b834f8885722dc5f56c326c817","tarball":"https://registry.npmjs.org/@dereiga/svelte-router/-/svelte-router-0.1.0.tgz","fileCount":12,"unpackedSize":33027,"signatures":[{"keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U","sig":"MEUCIQClootWxJ4QjEqZ/zweJoOQmb+Qo6OSs1oIbSzADgUYagIgT+V5os4ksJAYwQWFW5jWR59LgcWhdRIL8pnoojd59W4="}]},"_npmUser":{"name":"dereiga","email":"yudaaditya245@gmail.com"},"directories":{},"maintainers":[{"name":"dereiga","email":"yudaaditya245@gmail.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages-npm-production","tmp":"tmp/svelte-router_0.1.0_1780541608527_0.13100236363605422"},"_hasShrinkwrap":false}},"time":{"created":"2026-06-04T02:53:28.356Z","0.1.0":"2026-06-04T02:53:28.666Z","modified":"2026-06-04T02:53:28.844Z"},"maintainers":[{"name":"dereiga","email":"yudaaditya245@gmail.com"}],"description":"This template should help get you started developing with Svelte and TypeScript in Vite.","license":"MIT","readme":"# Svelte + TS + Vite\n\nThis template should help get you started developing with Svelte and TypeScript in Vite.\n\n## Recommended IDE Setup\n\n[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).\n\n## Need an official Svelte framework?\n\nCheck 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.\n\n## Technical considerations\n\n**Why use this over SvelteKit?**\n\n- It brings its own routing solution which might not be preferable for some users.\n- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.\n\nThis 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.\n\nShould 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.\n\n**Why `global.d.ts` instead of `compilerOptions.types` inside `jsconfig.json` or `tsconfig.json`?**\n\nSetting `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.\n\n**Why include `.vscode/extensions.json`?**\n\nOther 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.\n\n**Why enable `allowJs` in the TS template?**\n\nWhile `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.\n\n**Why is HMR not preserving my local component state?**\n\nHMR 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).\n\nIf you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.\n\n```ts\n// store.ts\n// An extremely simple external store\nimport { writable } from 'svelte/store'\nexport default writable(0)\n```\n","readmeFilename":"README.md","_rev":"1-8f4140126c09348f052940bf237cbae1"}