vike

🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin. (by vikejs)

Vike Alternatives

Similar projects and alternatives to vike

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better vike alternative or higher similarity.

vike reviews and mentions

Posts with mentions or reviews of vike. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-03-14.
  • SSRx vs. Vinxi vs. Vike - for SSR with Vite
    3 projects | dev.to | 14 Mar 2024
    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
    1 project | news.ycombinator.com | 16 Feb 2024
  • Triplit: Open-source DB that syncs data between server and browser in real-time
    7 projects | news.ycombinator.com | 12 Jan 2024
    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?
    1 project | /r/react | 26 Nov 2023
    Anyone have experience with https://github.com/vikejs/vike?
  • Waku: The Minimalist React Framework with Server Components
    3 projects | news.ycombinator.com | 27 Aug 2023
    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”
    13 projects | news.ycombinator.com | 15 Jul 2023
    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)
    1 project | /r/reactjs | 2 Jul 2023
    Maybe vite-plugin-ssr? It's pretty unopinionated and doesn't get in your way.
  • Next.js App Router Update
    4 projects | news.ycombinator.com | 22 Jun 2023
    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)
    2 projects | /r/react | 20 Jun 2023
    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?
    1 project | /r/reactjs | 30 May 2023
    vite-plugin-ssr
  • A note from our sponsor - WorkOS
    workos.com | 27 Apr 2024
    The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →

Stats

Basic vike repo stats
66
3,588
10.0
1 day ago

vikejs/vike is an open source project licensed under MIT License which is an OSI approved license.

The primary programming language of vike is TypeScript.


Sponsored
The modern identity platform for B2B SaaS
The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
workos.com