vike
commerce
vike | commerce | |
---|---|---|
66 | 47 | |
3,609 | 10,242 | |
3.1% | 1.6% | |
10.0 | 7.7 | |
6 days ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vike
-
SSRx vs. Vinxi vs. Vike - for SSR with Vite
Here are some collected notes of the distinctions between SSRx, Vinxi and Vike, to share with anyone else searching the web. Since my Google search came up empty, and I had to ask around on Twitter/X and GitHub to find out.
- Vike – Meta Framework Alternative
-
Triplit: Open-source DB that syncs data between server and browser in real-time
We're working on exactly this. You can already do this with Triplit but it's challenging to make an out of the box solution because each framework passes context/data different from server to client differently. There's a cool project called [Vike](https://github.com/vikejs/vike) that generalizes this pattern across SSR'd UI frameworks
-
Can't stand Next JS-- alternatives w/ Vite?
Anyone have experience with https://github.com/vikejs/vike?
-
Waku: The Minimalist React Framework with Server Components
have you seen https://vite-plugin-ssr.com/ ? i've only browsed their docs, but AFAICT their pitch that it's a more DIY approach to a framework, where you keep a lot of control over how things are wired together.
-
The theory versus the practice of “static websites”
I agree and, as the author of vite-plugin-ssr[1], that's what I recommend to my users: go for static whenever you can.
I think it's something every web developer should be aware of. Static is indeed a lot simpler than dynamic.
I've wrote more about it over here[2] (SSG = static, SSR = dynamic).
[1]: https://vite-plugin-ssr.com
-
What's the best ISR (and SSR) React frameworks? (looking for NextJS alternative)
Maybe vite-plugin-ssr? It's pretty unopinionated and doesn't get in your way.
-
Next.js App Router Update
Also have a look at https://vite-plugin-ssr.com/ (author here).
VPS is slightly lower level which gives you a lot more control: integrate with your existing Node.js backend (use any backend framework you want), deploy anywhere, use any React alternative (Solid, Preact, ...) and any data fetching tool (e.g. Relay can't really be used with Next.js).
The flip side is that you've to write a little bit more glue code. Although this will be alleviated by a lot with projects such as Bati[0], Stem[1], and vike-react (see Vike Rebranding[2]).
VPS also cares a ton about details, such as hooks for full control over i18n (use any i18n strategy you want), better Base URL support (VPS supports setting a different base for your server and your CDN), automatic deploy synchronisation, domain-driven file structure, polished and helpful error messages (especially the next upcoming release), ...
Detailed comparison with Next.js: [3].
If you run into any blocker then it's quickly fixed (or at least a workaround is proposed).
It supports not only SSR and pre-rendering, but also SPA in case you don't need SSR. It's going to support RSC but doesn't yet (RSC isn't ready for production).
Because it's lower level and because it's decoupled from React everything is designed in an agnostic way and with meticulous care. In other words: vite-plugin-ssr is becoming a robust foundation. There are breaking changes coming for the v1 release but beyond that chances are that there won't be any breaking change for years in a row.
In a nutshell: vite-plugin-ssr takes care of the frontend and only the frontend. You keep control over your architecture. (Whereas frameworks tend to put themselves right in the middle of your architecture restricting you in fundemetanl ways.)
Last but not least: it's powered by Vite which means blazing fast HMR.
[0] https://batijs.github.io
[1] https://stemjs.com/
[2] https://github.com/brillout/vite-plugin-ssr/issues/736
[3] https://vite-plugin-ssr.com/nextjs-comparison
-
React Server Side Rendering(SSR)
Now by default, Vite doesn't do SSR. One way to do Vite+SSR is to use vite-plugin-ssr. You can scaffold an example project that does SSR based on some dynamic data:
-
NextJS app router is complete failure, what alternatives do you recommend for react SSR and ISR?
vite-plugin-ssr
commerce
-
Ask HN: Modern self-hosted e-commerce solutions?
There are several open source solutions if you're interested... you can do a headless frontend with Vercel Commerce (Next.js) and use any of the supported e-commerce backends to manage catalog/cart/orders/etc: https://github.com/vercel/commerce
- Are there any best practices Next projects out there?
-
[Hiring] NextJS Developer
You need to use Medusa or Saleor as the backend (they are open source headless ecommerce backends). There already exists an amazing boilerplate and fully functional app for both of these: https://github.com/vercel/commerce
-
The Need for Speed: Does Store Performance Make or Break Success? Analyzing the Impact of Speed on Shopify Sites
Hey everyone, I stumbled upon an intriguing website recently, built using Shopify, the platform notorious for its sluggish performance. However, to my surprise, this particular site managed to achieve a perfect 100 score thanks to NextJs. I know this community is well-versed in website performance, so I thought I'd share it with you all. To be honest, I've been pondering the significance of speed when it comes to the success of online stores. Can a few milliseconds really make or break a business? We often hear the phrase "Milliseconds Make Millions," and I wonder if it holds true in reality. What are your thoughts on this? In today's digital landscape, it seems like everyone is using Shopify, making it the go-to platform for setting up an online store. But is being the fastest fish in the pond the key to outperforming the competition? Does speed truly matter when it comes to customer experience and ultimately achieving financial success? I'm genuinely curious to hear your insights and experiences regarding the impact of website speed on online businesses. Do you believe that optimizing every millisecond can lead to substantial gains, or is it more of a minor factor in the grand scheme of things? Let's have an open discussion about the role of speed in the success of Shopify sites and how it aligns with our experiences and beliefs. I invite you to share your thoughts and contribute to this conversation. No sales pitches or hidden agendas, just an honest exploration of the topic. Looking forward to hearing your perspectives! Best regards, CuriousRedditor
- The app router is not production-ready yet
-
Advice needed: Nextjs e-commerce learning
Next.js has an official e-commerce template here: https://github.com/vercel/commerce
-
svelte-commerce: Open Source fronted for any e-commerce. Works with Shopify, MedusaJS, Litekart, BigCommerce.
This is great, especially as Next.js commerce has decided to go shopify only - https://github.com/vercel/commerce/pull/966 - making a full open-source solution impossible.
-
What headless CMS would you choose for NextJS e-commerce project?
Vercel also have an example for it. https://github.com/vercel/commerce/tree/main/packages/swell
- Real-world react app with great architecture in 2023
-
Has anyone created a Shopify app with Next-Auth?
Vercel Commerce
What are some alternatives?
vite-ssr - Use Vite for server side rendering in Node
next-auth - Authentication for the Web.
Next.js - The React Framework
next-auth-sanity - NextAuth Adapter and Provider for Sanity
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
headwind - An opinionated Tailwind CSS class sorter built for Visual Studio Code
ts-node - TypeScript execution and REPL for node.js
vendure - A headless GraphQL commerce platform for the modern web
vite-plugin-vue2 - Vue2 plugin for Vite
substrate - Substrate: The platform for blockchain innovators
nextjs-tailwind-ionic-capacitor-starter - A starting point for building an iOS, Android, and Progressive Web App with Tailwind CSS, React w/ Next.js, Ionic Framework, and Capacitor