181–190 of 202 posts
Earlier quoted context omitted.
What an asinine interpretation. No thanks.
I agree. It's up to the publisher to decide the significance of version numbers. Just because Node does it one way doesn't mean everyone else has to follow suit.
That’s the sole reason for the squiggly marks and carets that exist in every package.json.
Earlier quoted context omitted.
The description is maybe a little misleading. Vite is a development experience improvement for existing frontend frameworks; most people using it are on React or Vue (which is the other of the "big 3" along with React and Angular). It's about making projects build and start faster.
For clarification, isn't it true that you can only use Vite with Vue and React, and not Angular. Angular is too tied to WebPack (At least not today) I am not entirely sure, so I wanted to ask.
Some folks have attempted it, but not completed vite support.
This is nothing new in angular land. There are multiple third party libraries and framework which support react, vue, svelte and even solid, but not angular.
I know, it still seems crazy what's happening at the frontend ... but Vite brings substantial advantages compared to the old standard. Same thing with the next-gen frameworks like Svelte, SolidJS or Vue 3 (composition API) that are substantially better than the old ones (mainly regarding DX). Another welcoming example are the quite new E2E testing frameworks like Cypress or Playwright.
The funny thing is that I hate changing tech at the backend, but still love many of the innovations at the frontend. I know, it still seems crazy what's happening at the frontend ... but Vite brings substantial advantages compared to the old standard. Same thing with the next-gen frameworks like Svelte, SolidJS or Vue 3 (composition API) that are substantially better than the old ones (mainly regarding DX). Another w…
Earlier quoted context omitted.
I agree that frontend stuff moves too fast in general, but Vite specifically is a good change. Frontend build systems are a mess (and often slow) so I welcome tools that improve the situation
It doesn't move fast. It creates a lot of noise fast. It's like having a chicken running around, but it gets nowhere
Earlier quoted context omitted.
I agree. It's up to the publisher to decide the significance of version numbers. Just because Node does it one way doesn't mean everyone else has to follow suit.
The entire NPM ecosystem is based on semver. That’s the sole reason for the squiggly marks and carets that exist in every package.json.
Earlier quoted context omitted.
Major version bump !== Your app breaks
According to semantic versioning, a major version indicates breaking changes, which is always bad from a users perspective. Most projects don't really use semver anymore though, which is why this association seems to be going away
I had no idea so many other frameworks are using Vite as their default. Event server-side frameworks are picking it up! Has Webpack really been dethroned as the go-to bundler?
Otherwise I've been using Parcel without much issues with quite less configuration.
Earlier quoted context omitted.
The entire NPM ecosystem is based on semver. That’s the sole reason for the squiggly marks and carets that exist in every package.json.
Quoted post unavailable.