With most of the documentation still "Coming soon", I really appreciate you taking the time figure out how to get it up and running by diving into the examples.
I don't like file-based routers and I don't need SSR in my pet project, but I enjoy the convenience of server functions. Recently, I created a standard SPA React app with the ability to call server functions. Thanks, Vinxi! It's important to mention that adding this functionality took only a few minutes. I think it would be a great idea for your next video to showcase a similar setup
Thank you for the very informative video today. I was happy to see you use pnpm. Can you make a video about monorepo such as pnpm or Nx? Thank you always :)
Is it possible to extend this a little to show how it works in production? I've only been using Vite for static building of my SPA currently, not as a production server, so would be interested to see how that works, and then how Vinx works on top of Vite to make that even better.
Vinxi is really a MetaRouter (built on top of a web server, H3/Nitro). Since its core thing is that it allows you to compose routers. It routes between routers.
Just a heads up, I think the node team wants to deprecate corepack. Probably won’t happen for another five years though, lol. I think nix devenv is a good solution for node and package manager installations, instead.
The reason you don't need to use a useEffect anymore, is because in SSR pages, you can just async/await your api calls directly. However, since you're using client-side state, you still have to do it anyway
While its a slightly quicker dev experience in general (especially within meta frameworks like solid start) i still find vinxi and all other js https server implementations much less performant than using golang for apis, and have to be certain the service will never have a high user base for me to feel comfortable using JS apis.
it's server close the the client, but it can be rewritten in go or rust, the point is that, u don't need fullblown framework. Btw, the BE server api endpoints are least important if they are written in go or js (besided different handling of GC), u will sooner or later ends up wtih CQRS for performance issues.
AFAIK you can 100% use bun for the install. Not sure if you can run it with bun. But it would be a bun problem if you can't. It's not the job of library/framework authors to make their code Bun compatible. It's the job of Bun to be compatible with frameworks and libraries.
@@viniciusataidedealbuquerqu2837 Next.JS isn't vendor locked. I'm building a monolith server with Appwrite and Next.JS using TrueNAS Scale and Docker. The good thing about Appwrite is that you can use their cloud, it has in-memory caching, and then transfer into a 64 or 128-core server you can upgrade to 2TB RAM, multiple petabytes of hard drives and U2 NVMe. By the time you exhaust those resources, you will have so much money coming in someone else can deal with it. It's more important to have your database and server on the same server with in-memory caching than it is to have a horizontally scaled service you may never need that much power for.
Solidstart? Thats a framework. Vinxi? Thats a meta-meta-framework. Vite? Thats the meta-framework that the meta-meta-framework vinxi uses to power the framework solidstart.
I guess it's a sign of success that my first comments are always bots with sexy avatars making generalized comments. I'm not sure what it gets them though.
With most of the documentation still "Coming soon", I really appreciate you taking the time figure out how to get it up and running by diving into the examples.
I couldn't figure out the docs, I know this is what solid uses. I'll follow this, love vite! great content as always
Check examples folder in vinxi repo
Great content pops. I hope you're doing well ❤
I am. And thank you!
Also, thanks a lot for sharing the source code. I've been learning a lot with you lately 🙏
I don't like file-based routers and I don't need SSR in my pet project, but I enjoy the convenience of server functions.
Recently, I created a standard SPA React app with the ability to call server functions. Thanks, Vinxi!
It's important to mention that adding this functionality took only a few minutes.
I think it would be a great idea for your next video to showcase a similar setup
Great video! I hadn't heard of Vinxi (and wouldn't have pronounced it like that - ha). Thanks!
More Murph-driven projects please. Great video as always!
Thanks Jack! I would be really curious to explore what the build output looks like!
It’s exactly vite for the client side and the server side is a nitro build.. but basically a bundled node script kinda thing
Cool. First time heard of Vinxi.
I guess next time you are going to talk about pnpm workspace, or monorepo thing, sharing code/components/hooks among multiple next.js apps. 🥰
Great idea
It sounds like you want me to talk about that. :)
@@jherr Yes! Yes! Please do!
@@jherr coolify + turbopack builds with caching at some point maybe?
Would be nice to compare this with vite ssr server.js. That feels more straightforward but equally experimental.
Thank you for the very informative video today. I was happy to see you use pnpm. Can you make a video about monorepo such as pnpm or Nx?
Thank you always :)
Cool! Thank you for the nice overview!
Thanks for your awesome video. If possible, please create a video about honojs + vitejs
Great content, I just arrived to your channel and I am so happy. Great quality,,
Is it possible to extend this a little to show how it works in production? I've only been using Vite for static building of my SPA currently, not as a production server, so would be interested to see how that works, and then how Vinx works on top of Vite to make that even better.
Vinxi is really a MetaRouter (built on top of a web server, H3/Nitro). Since its core thing is that it allows you to compose routers. It routes between routers.
Yep. You can literally create several APIs in your project (one in Hono and one in Express, for example).
Just a heads up, I think the node team wants to deprecate corepack. Probably won’t happen for another five years though, lol.
I think nix devenv is a good solution for node and package manager installations, instead.
Never a dull moment in node land.
Corepack vid yes please! ❤
Webdev is up to the roof!
Nice explanation on Vinci! I wonder if I can Inject that with an electron app :D :D
Great video!!
The reason you don't need to use a useEffect anymore, is because in SSR pages, you can just async/await your api calls directly. However, since you're using client-side state, you still have to do it anyway
just wire it with tanstack query, and u don't need useEffect at all, nor client state, unless u need to set some current item
sick
While its a slightly quicker dev experience in general (especially within meta frameworks like solid start) i still find vinxi and all other js https server implementations much less performant than using golang for apis, and have to be certain the service will never have a high user base for me to feel comfortable using JS apis.
it's server close the the client, but it can be rewritten in go or rust, the point is that, u don't need fullblown framework. Btw, the BE server api endpoints are least important if they are written in go or js (besided different handling of GC), u will sooner or later ends up wtih CQRS for performance issues.
Absolutely typical.. I build something that was now extremely simplified two weeks later.
Have you tried vike?
I have not. I'll give it a look.
Fantastic.
time to rewrite my project 🎉
You don't need to do this if you used Vite before
This is cool!
Great content @jherr
I do have a question
What would the difference be if I were to use Bun instead of PNPM/NPM/Yarn?
AFAIK you can 100% use bun for the install. Not sure if you can run it with bun. But it would be a bun problem if you can't. It's not the job of library/framework authors to make their code Bun compatible. It's the job of Bun to be compatible with frameworks and libraries.
Yup can both install with bun and run with bun .. which actually runs vinxi in node.. but you can do bun run dev -bun and that’s pure bun magic
@@jherr Thank you
@@devinxi Thank you
What is better in 2024: Vite with Vinxi or Next.JS 14?
vendor locking is a bitc* so vinxi it is
@@viniciusataidedealbuquerqu2837 Next.JS isn't vendor locked. I'm building a monolith server with Appwrite and Next.JS using TrueNAS Scale and Docker. The good thing about Appwrite is that you can use their cloud, it has in-memory caching, and then transfer into a 64 or 128-core server you can upgrade to 2TB RAM, multiple petabytes of hard drives and U2 NVMe. By the time you exhaust those resources, you will have so much money coming in someone else can deal with it. It's more important to have your database and server on the same server with in-memory caching than it is to have a horizontally scaled service you may never need that much power for.
I'm going to go with NextJS because it's a canned complete solution. Vinxi to me feels like SPA++.
Depends what u wanna build
Solidstart? Thats a framework. Vinxi? Thats a meta-meta-framework. Vite? Thats the meta-framework that the meta-meta-framework vinxi uses to power the framework solidstart.
solid is a framework, and solidstart is its metaframework (that uses the metaRouter Vinxi). Now try again😅
full typescript stack
How do we do ssr? Also, can we have filesystem based routing?
Yes and yes. But the file based routing is currently at
"experimental" level./
is there anything similar for Hono? Like how Vinxi is for Nitro
is vinxi could run solidJS + ReactJS each one on a router via plugin in one app ?
Yep.
@@jherr Its amazing
Please do VikeJS (vite-plugin-ssr)!
Fatal flaw? Come on.. 🤣
It's RUclips. I gotta push the clickbait a little. :)
I actually thought they fixed that memory issue on bigger projects, that's the real fatal flaw.
I love you. But man, a meta meta framework. Where did we take the wrong turn?
Why tho, i like it
Vinxi is a meta-router which is used in meta-frameworks like SolidStart.
What's up with all these comments 😂 lol
Haha I don't know but they are not wrong!
I guess it's a sign of success that my first comments are always bots with sexy avatars making generalized comments. I'm not sure what it gets them though.
What about remix?
What about remix?
@@jherr They migrated to vite, so remix is now a vite plugin :-) I though you might like it?
@@ChristianMoentest Sure. Yeah. It's good stuff.
can you deploy this on vercel?
Yes
Just use Nitro tbh.