https://github.com/semanticdata/pwa-svelte
Dashboard with different toggable widgets and resizable grid.
https://github.com/semanticdata/pwa-svelte
daisyui pwa svelte tailwindcss typescript
Last synced: 6 months ago
JSON representation
Dashboard with different toggable widgets and resizable grid.
- Host: GitHub
- URL: https://github.com/semanticdata/pwa-svelte
- Owner: semanticdata
- Created: 2025-04-03T21:26:06.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2025-04-30T17:52:42.000Z (10 months ago)
- Last Synced: 2025-06-05T22:38:52.278Z (8 months ago)
- Topics: daisyui, pwa, svelte, tailwindcss, typescript
- Language: Svelte
- Homepage:
- Size: 106 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# PWA Digital Clock with Weather
A Progressive Web Application built with Svelte and Vite, featuring a digital clock and weather display. The app showcases modern web development practices with a beautiful, responsive UI powered by TailwindCSS.
## Features
- Real-time digital clock display
- Date display with full formatting
- Weather information display (coming soon)
- Progressive Web App capabilities
- Responsive design with TailwindCSS
- Modern, clean UI with backdrop blur effects
## Tech Stack
- Svelte 5
- Vite 6
- TailwindCSS
- PWA features (Service Workers)
## Ideas
- Pomodoro timer
- Alarm clock
- Stopwatch
- To-do list (https://ticktick.com/)
- Calendar
- Music player widget (spotify?)
- Notes widget
- Quotes widget (https://wordsmith.org/)
## Getting Started
### Prerequisites
- Node.js (Latest LTS version recommended)
- npm or yarn
### Installation
1. Clone the repository
2. Install dependencies:
```bash
npm install
```
### Development
Run the development server:
```bash
npm run dev
```
### Building for Production
Create a production build:
```bash
npm run build
```
Preview the production build:
```bash
npm run preview
```
## Recommended IDE Setup
[VS Code](https://code.visualstudio.com/) + [Svelte](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode).
## Technical Considerations
**Why use this over SvelteKit?**
- It brings its own routing solution which might not be preferable for some users.
- It is first and foremost a framework that just happens to use Vite under the hood, not a Vite app.
This template contains as little as possible to get started with Vite + 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.
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.
**Why `global.d.ts` instead of `compilerOptions.types` inside `jsconfig.json` or `tsconfig.json`?**
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.
**Why include `.vscode/extensions.json`?**
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.
**Why enable `checkJs` in the JS template?**
It is likely that most cases of changing variable types in runtime are likely to be accidental, rather than deliberate. This provides advanced typechecking out of the box. Should you like to take advantage of the dynamically-typed nature of JavaScript, it is trivial to change the configuration.
**Why is HMR not preserving my local component state?**
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/sveltejs/svelte-hmr/tree/master/packages/svelte-hmr#preservation-of-local-state).
If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
```js
// store.js
// An extremely simple external store
import { writable } from 'svelte/store'
export default writable(0)
```