EvanYou

7 ms·

1.
by EvanYou 11mo ago
Wrong - Vite is not open core, Vite+ is. This differentiation is important because even if a feature benefits Vite+, if it needs to be shipped via Vite then it has to be open source. Companies willing to pay for Vite+ help sustain and impro
2.
by EvanYou 11mo ago
Good question. The first and most important distinction is obviously which ecosystem you are more familiar / invested in (webpack vs. vite). It does make sense for projects deeply coupled to webpack to consider rspack first. Putting th
3.
by EvanYou 11mo ago
A rugpull means taking back something that was given. Before Vite+, we maintain Vite, Rolldown, Oxc, all of which are open source and widely used. These remain open source - nothing changes about existing projects. Vite+ is an entirely new
4.
by EvanYou 11mo ago
Not even Rollup. Vite+ uses Rolldown which is also developed from the ground up by VoidZero.
5.
by EvanYou 11mo ago
Vite+ is built on top of the Rust stack (Rolldown / Oxc) developed by the same team and uses none of these.
6.
VoidZero: Building a Unified Toolchain for JavaScript(voidzero.dev)
34 points by EvanYou 2y ago|6 comments
7.
by EvanYou 2y ago
Note in the benchmark, it is comparing a React JSX project using @vitejs/plugin-react (Babel based) instead of @vitejs/plugin-react-swc (SWC based). I made the exact same point two years ago when Turbopack came up with a similar b
8.
by EvanYou 3y ago
For esbuild: We know other teams that have attempted to improve code splitting based on esbuild and found it very difficult. A big part of it is that in order to be fast, esbuild applies multiple features (bundle, treeshaking, transforms) i
9.
by EvanYou 3y ago
I’m specifically taking about non-component context, i.e. plain JS/TS files. Previously Svelte was able to get a pass on this because magic only happens in svelte files - but in the future, any JS/TS files in a rune-enabled Svelte
10.
by EvanYou 3y ago
> $state and $ref are quite different. I wouldn't say they are "different" - they are fundamentally the same thing: compiler-enabled reactive variables backed by runtime signals! But yes, Vue already exposes the underlying
11.
by EvanYou 3y ago
This is (surprisingly) almost identical to the Reactivity Transform explorations we did in Vue: https://vuejs.org/guide/extras/reactivity-transform.html let count = $ref(0) const double = $computed(() =>
12.
by EvanYou 4y ago
Author of Vue here - as many have pointed out, the article contains a number of comparisons that are incorrect. I have written a post clarifying them: https://blog.vuejs.org/posts/on-migration.html
13.
by EvanYou 4y ago
This analogy is plain wrong. The blog post lists multiple non-Vue frameworks/tools using Vite as their default build tool. Compare that to the number of non-JS languages (excluding ones that compile to JS) using NPM as their default pa
14.
by EvanYou 5y ago
I do know Henry personally and Henry actually consulted me when he was debating whether he should quit his job to work on Babel full time. We also occasionally talk about the burdens of OSS maintenance so I know first hand how hard he'
15.
by EvanYou 5y ago
Proper Jest integration is blocked by async transformers ( https://github.com/facebook/jest/pull/9889 ) which should land as part of Jest 27, so we are mostly waiting on that. In the meanwhile, you can also con
16.
by EvanYou 5y ago
At this point I don't think I really want to "sell" it to anyone. I've got enough things to maintain so I'd rather just have users who use Vite because they actually like it rather than people switching from webpack
17.
by EvanYou 5y ago
FWIW that plugin does not make your existing webpack-based code magically work in snowpack. It's just using webpack to bundle your snowpack-based code.
18.
by EvanYou 5y ago
Author of Vite here. I see many people evaluating Vite as a webpack replacement, so I want to clarify the goal of the project here: It is NOT Vite's goal to completely replace webpack. There are probably a small number of features&#x2F
19.
Vite 2.0 Released(vitejs.dev)
6 points by EvanYou 6y ago|2 comments
20.
by EvanYou 6y ago
> Having to write two type definitions for Component Props: one TS interface/type, and one as the JS object sucks. Uh, you don't have to? TS inference works with the JS objects. There's no need to provide the generic argum
21.
by EvanYou 6y ago
It's not that we can't implement it like that, the real challenge is in minimizing breakage from v2. We decided it's better to not completely alter how props are declared because that would be too much breakage. Instead, ther
22.
by EvanYou 7y ago
AFAIK there is currently no plan to replace existing php rendering with Vue SSR. They just wanted to make sure the framework they went with supports SSR so they are not locking themselves out of the possibility. The HN implementation render
23.
by EvanYou 7y ago
Team lead of Vue.js here. Clarifying a few points being raised in this thread: - This does not mean Wikipedia is becoming an SPA. One of the reasons they picked Vue is because Vue can be used to progressively enhance a statically rendered p
24.
by EvanYou 7y ago
Who said they are going to make the entire page SPA? They picked Vue specifically because Vue allows them to progressively enhance parts of the page with interactivity without going full SPA (AND without hard reliance on a build step).
25.
by EvanYou 7y ago
Let's get the logic straight here: - The Vue project has more than 20 core team members and hundreds of contributors from all over the world. There are currently TWO active core team members working for big companies in China. - These
26.
by EvanYou 7y ago
First of all, this new API has relatively little to do with performance. The main performance gain in Vue 3 comes from a new template compilation strategy invisible to users. Second, I think it is over-simplifying the issue by equaling the
27.
by EvanYou 7y ago
Vue team lead here. There is a lot of FUD in this thread so we need to clarify a bit: - This API is purely additive to 2.x and doesn't break anything. - 3.0 will have a standard build which adds this API on top of 2.x API, and an o
28.
by EvanYou 8y ago
Author here - this was just a weekend hack and didn't really expect it to show up here, but thanks for the security related feedback. The setup now uses environment variables.
29.
by EvanYou 8y ago
FWIW, the GitHub age isn't entirely accurate because both React and Vue had major rewrites and the current default branch doesn't hold the entire development history. Vue's first public release was Feb of 2014 and React is ju
30.
by EvanYou 8y ago
Not sure why this is the primary concern but... did you even try it? Webpack is really an internal implementation detail for VuePress and not visible at all in most use cases.

More ›