skewer-mode VS vite

I am trying to get skewer-mode to work, in particular, I want to see changes I make to html files in emacs to be automatically updated in the corresponding browser window. I have tried to follow the descriptions on the package's GitHub page and also this Emacs Stack-Exchange post, but neither of these affords me the "live change" I seek, and most other guides don't regard HTML, but only CSS or Javascript (which I'll also need, but that's for later).

Yes, sure. It depends on what language you use. Here is LSP in emacs. This one is like live server on vs code.But if you use something like Django I think you don't have to worry about live server. .

I've been looking around for a bit and the closest I found was skewer, but I can't seem to get it to work and it doesn't seem to be quite what I want either. All I need is to be able to serve a directory as an HTTP server and have it auto-reload in my browser when I save any of the js, html, css, etc files in the directory.

As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/