Patedam
2916ad9c99
commite8b53dc953Author: Patedam <pgillen.pro@gmail.com> Date: Tue Mar 3 01:15:17 2026 -0500 Updated backend to make sure it works properly with frontend. Fixed one frontend issue (free heap was not correctly named) commit3428808f83Author: Patedam <pgillen.pro@gmail.com> Date: Tue Mar 3 00:36:01 2026 -0500 Fixing various build errors. Activated minimal build commit59364ac22dAuthor: Patedam <pgillen.pro@gmail.com> Date: Tue Mar 3 00:03:24 2026 -0500 Added info and reboot api into the backend. Created the basics for a backend server. commit37291557ebAuthor: Patedam <pgillen.pro@gmail.com> Date: Mon Mar 2 23:05:10 2026 -0500 feat: Add API endpoints for system reboot and retrieving system information. commita010b0c352Author: Patedam <pgillen.pro@gmail.com> Date: Mon Mar 2 22:56:13 2026 -0500 Added AgentTasks into git ignore we will use it to store current tasks so we can createnew contexts chat when its too big commit75bab78137Author: Patedam <pgillen.pro@gmail.com> Date: Mon Mar 2 22:42:29 2026 -0500 feat: Initialize ESP-IDF project with core build configuration, component dependencies, and web frontend deployment. commitbba4c63f93Author: Patedam <pgillen.pro@gmail.com> Date: Mon Mar 2 22:21:52 2026 -0500 docs: Add backend architecture documentation for the ESP32-S3 provider.
Svelte + Vite
This template should help get you started developing with Svelte in Vite.
Recommended IDE Setup
Need an official Svelte framework?
Check out SvelteKit, 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.
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 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.
If you have state that's important to retain within a component, consider creating an external store which would not be replaced by HMR.
// store.js
// An extremely simple external store
import { writable } from 'svelte/store'
export default writable(0)