core

You're looking for `@vue/reactivity`[1] - looks like it provides ref, computed, watch, and some internals. Honestly, this seems pretty nifty. Most projects I'd do today would likely have more value in Vue as a whole, and it's nice to see these kinds of things exposed and standalone bits [1] https://github.com/vuejs/core/tree/main/packages/reactivity/...

Solid.js and Vue uses these sorts of tricks to shave the amount of bytes from the HTML templates they generate https://github.com/vuejs/core/commit/30dbdc101a48d747b56bcdd...

Is the difference between the number of dev dependencies for eg. VueJs (a JavaScript library for marshalling Json Ajax responses into UI) and Htmx (a JavaScript library for marshalling html Ajax responses into UI) meaningful? There is a difference, but it's not an order of magnitude and neither is a true island. Granted, deciding not to use JS on the server is reasonable in the context of this article, but for the client htmx is as much a js lib with (dev) dependencies as any other. https://github.com/bigskysoftware/htmx/blob/master/package.j... https://github.com/vuejs/core/blob/main/package.json

> Yes, I do go after those frameworks I'll believe that once I see you file an issue which mentions accessibility against any of the projects I linked to ;-) https://github.com/facebook/react/issues?q=is%3Aissue+author... https://github.com/vuejs/core/issues?q=is%3Aissue+author%3As... https://github.com/sveltejs/svelte/issues?q=is%3Aissue+autho...

`@vue/compiler-sfc` which powers the vite Vue 3 SFC plugin (`@vitejs/vue`) has a dependency on the `@babel/parser` package[0] That's the dependency I am speaking to here [0]: https://github.com/vuejs/vue-next/blob/master/packages/compi...

Yes, templates are different. That's why I said that they're "specific DSLs ... compiled into a JS render function" Anyway there is no other abstraction. Hooks and composition APIs aren't magic, they're functions that you can write yourself. It's basic property change notifications but wrapped up in various levels of automation. Vue's object API can definitely seem messy but the new composition APIs in Vue 3 is standard JS syntax. Maybe it would be helpful to see the code yourself: https://github.com/vuejs/vue-next/tree/master/packages/react...

The topic is that all code is text, and everything can be parsed and understood based on specific language grammars, even if they're embedded within each other. What are you even arguing at this point? This isn't about compilation or strings anymore. You don't like Vue's specific DSL? Or you don't understand it? Or you found a problem with the documentation? Or do you need a full grammar and syntax definition before you can do anything? It's basically any valid `for..in/of` expression but you can always solve your mystery of "who knows" by just looking at the source code: https://github.com/vuejs/vue-next/blob/master/packages/compi...

I wish the submitter added their comment or gave some context, if there is any. For me this is an arbitrary number for a random popular repository. Especially since the linked github project https://github.com/vuejs/vue is not the latest version of vue (see: https://github.com/vuejs/vue-next ).

Here's the Vue PR with the changes necessary: https://github.com/vuejs/vue-next/pull/1483

I believe v3 is on their github as https://github.com/vuejs/vue-next