{"_id":"@base.cat/svelte-timetracker.ts","name":"@base.cat/svelte-timetracker.ts","dist-tags":{"latest":"1.0.0"},"versions":{"1.0.0":{"name":"@base.cat/svelte-timetracker.ts","private":false,"version":"1.0.0","author":{"name":"Octavi Fornés","email":"ofornes@base.cat"},"type":"module","scripts":{"dev":"vite","build":"vite build","preview":"vite preview","check":"svelte-check --tsconfig ./tsconfig.json"},"devDependencies":{"@smui-extra/badge":"^6.0.0","@smui/button":"^6.0.0","@smui/common":"^6.0.0","@sveltejs/vite-plugin-svelte":"^1.0.0-next.30","@tsconfig/svelte":"^2.0.1","svelte":"^3.52.0","svelte-check":"^2.2.7","svelte-preprocess":"^4.9.8","tslib":"^2.3.1","typescript":"^4.5.4","vite":"^2.9.9"},"dependencies":{"idb":"^7.1.1","moment-timezone":"^0.5.38","sveltestrap":"^5.10.0"},"gitHead":"7f96dcee6ea02dd5b32dbb2ef81b0845608ac5b1","description":"This template should help get you started developing with Svelte and TypeScript in Vite.","_id":"@base.cat/svelte-timetracker.ts@1.0.0","_nodeVersion":"16.18.1","_npmVersion":"8.13.2","dist":{"integrity":"sha512-mLZLrHXLnSgqZboIfX+ihhHaCgidJJfuElzW2RXB9g6IeXe58zrI6MbVVyzeaJtnn0cdfBx5fq8JEUc0/uDHyQ==","shasum":"b8757cff34775eabf410ef3ea52c53ca4acb29a5","tarball":"https://registry.npmjs.org/@base.cat/svelte-timetracker.ts/-/svelte-timetracker.ts-1.0.0.tgz","fileCount":19,"unpackedSize":23455,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDkcWFR4i2KsQEI8HMEOzVVNIq6npm90un6D3j96QCtkQIhAKryHf0SrM7xzNF3BkUHIUvC22BhIjJmJy7nb60cymZJ"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJja1QQACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmr7Wg/+LnYosZzPl/+BQhGlpO2bBm7TPI3ZzewRYZwyjnbxxqeX0yap\r\nVqWRNvSyFhvX0Uhdv3v9cA3JAzEl4FAK9jr0dbmvd88UgQF9JjwdyByGn4PI\r\nFyx2cby8BCL2YSmxzPDUUh9Jeo+S9jxIXvqOH5H6LcAnuLDEDSAFTCVl4QLX\r\nFEFbGKvFB+Y3a+hC8eGfm2v2HSCPJu1MT279mgXxDwrvMRLOdEiy2XGtMVNS\r\nU2+Utg8FETDLMpg3tTowy4bBJ8cZm2+HCjr8WGFu43KiGIHE4utBw/pGeuQ0\r\nnA01OQOjB4Cl1VxF0Mvn2pD1kzu/tAMwnh/RU2n90H99PlHAcaY6GvCGX6Pa\r\nTgyfSG5tDi7GuGWvdwzFzaG5EHr8WwZMQ23C79qP1B5AeffwyOdyx6qJ2na6\r\nh1fCISMvyZW7j06XrljRyLieTipzLEezfNVRW8em6Y1P0UPf566jrXIQntvE\r\n4z1YfePN0rbQivPqJrLmkQlqQFLeN+/4bjsaLLi/6LaacBMVF8utAGD+urpC\r\n1hCDpZD3G3kvE4dZ9mRnJYSiypg0dkN6wcANiH6lXURugbwiqP5xGpcA/E1V\r\nAbBnhhiuk+1/4GelmnMEfWXTnS9xtU0pXRE1Js5pFFnA+mW+QYVXNaIrWmty\r\nb6etm0u4rr2GJ/DUGws4gyAHMba5jpOJ+KQ=\r\n=sBDk\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"ofornes-base","email":"ofornes@base.cat"},"directories":{},"maintainers":[{"name":"ofornes-base","email":"ofornes@base.cat"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/svelte-timetracker.ts_1.0.0_1667978256150_0.02440416473758189"},"_hasShrinkwrap":false}},"time":{"created":"2022-11-09T07:17:36.083Z","1.0.0":"2022-11-09T07:17:36.274Z","modified":"2022-11-09T07:17:36.388Z"},"maintainers":[{"name":"ofornes-base","email":"ofornes@base.cat"}],"description":"This template should help get you started developing with Svelte and TypeScript in Vite.","author":{"name":"Octavi Fornés","email":"ofornes@base.cat"},"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  `vite dev` and `vite build` wouldn't work in a SvelteKit environment, for example.\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"}