vite

This is straight out of the horses mouth: - Lightning-fast cold server start - Instant hot module replacement (HMR) - True on-demand compilation This part should be of particular interest to you: https://github.com/vitejs/vite#how-is-this-different-from-vu...

This is what you'd expect, but he is very hands-on trying out technical ideas. I would look through his tweets to see the things he gets involved with. Recently he built Vite to see if it'd be possible to have a dev setup with no bundling (just using ES modules). It's evolved since then, but he picks up work a lot on new ideas and seeing how it can drive the direction of Vue. https://github.com/vitejs/vite#how-and-why

> If you just want to try Vue 3 out - you can do it right now with Vite. Vite (https://github.com/vitejs/vite) is a new dev/build tool that we created that is lighter, faster and produces smaller bundles. It works with Vue 3 out of the box. From https://github.com/vitejs/vite: > Vite is an opinionated web dev build tool that serves your code via native ES Module imports during dev and bundles it with Rollup for production. I wonder if Vite/Rollup will end up replacing vue-cli/webpack in the Vue community.

Anyone using Vue3? How's it going? I am very much looking forward to migrating to V3 and using TypeScript for components. The new vite [0] dev tool looks impressive. The features list is chock full of good stuff like TypeScript, JSX, CSS processing, hot reloads, JSON and CSS loading, etc. [0] https://github.com/vitejs/vite

I can fully understand that an additional tool layer can cause additional problems, but static type checking is a large quality win for large projects. There are workarounds to achieve similar results: (1) Use a faster bundler like esbuild, here vite's similar considerations [1] (2) Use Flow [2] and just strip it away before distribution like this Babel module [3] --- [1] https://github.com/vitejs/vite#typescript [2] https://flow.org/ [3] https://babeljs.io/docs/en/babel-plugin-transform-flow-strip...

Thanks for the kind words! 1. I'm working on the admin panel, but it's not yet ready. I'm still hesitating how to approach the persistence layer without introducing too many abstractions. Generally speaking, I'd like to avoid ORMs as much as possible. :) 2. I use the node-pg-migrate [1] for migrations at the moment, but I plan to tightly integrate with Postgraphile / Hasura to give another approach for that part. 3. You need to add them manually, but the architecture is pretty close to Vite [2]. You have just one Node process for both front-end & back-end: in development I compile assets on the fly using ESBuild [4], in production I bundle them using Rollup. I should probably describe that in the docs more clearly :) In contrast to Vite, Kretes also provide a REST API out-of-the-box, and a relatively simple path for adding a GraphQL endp

I've felt exactly that while testing Vite (https://github.com/vitejs/vite) this morning from Evan You, author of VueJS. Standard install, nothing to configure, instant hot reload + modern code and tooling yet no perceivable latency for anything. It felt like suddenly I could enjoy front end dev. So I get the appeal of Deno. But I know this ability to put arbitrary URLs as dependancies in the code are going to be terribly missused and abused. I can see all the tutorials that will start including them, the bad architecture decisions that will spread them accross all files, the interns that will use localhost there, the typo and domain squatting or black SEO, the rise of people just telling you to put an URL from their site (the same that tell you to curl that bash script), the split from npm, the hardship of scanning/mapping/updating depend

Vite and Snowpack are a little different, though definitely similar in many regards. There's some good info here: https://github.com/vitejs/vite#how-is-this-different-from-sn... The salient points seem to be: 1. "Vite is more opinionated and supports more opt-in features by default - for example, features listed above like TypeScript transpilation, CSS import, CSS modules and PostCSS support all work out of the box without the need for configuration." 2. "Both solutions can also bundle the app for production, but Vite uses Rollup while Snowpack delegates it to Parcel/webpack. This isn't a significant difference, but worth being aware of if you intend to customize the build."

> The only thing that still sucks is UI frameworks, because all major frameworks still require a shitty babel workflow in one form or the other. Vue.js has an ESM module which is useless without babel (due to the .vue file format), and Angular/React are still in the lets-invent-our-own-language fatigue. The pain is real. Create-react-app will dump 250 MB+ of files in node_modules however, newer approaches are emerging and (hopefully) will be stable soon. few noteworthy ones are: 1. SnowPack[0] (in early access) 2. Vite[1] (from author of Vue.js) . It is in experimental phase. but is quie good. 3. Unnamed project by Author of Preact. [0] https://www.snowpack.dev/ [1] https://github.com/vitejs/vite [2] https://twitter.com/_developit/status/1264062182326710273