razzle VS vite

Documentation

You don't need NextJS for SSR. There are less opinionated alternatives like Remix that was built by the React Router team and is backed by Shopify now, you can use something like Razzle or one of its alternatives for semi-opinionated pure SSR or follow the Vite Docs and just do it yourself with express.

Razzle: I've never used it personally, but based on what I can tell it seems to be an attempt to enhance the Create React App concept, enabling CSR/SSR while also working well with libraries other than React.

Razzle is a tool for building Universal applications: applications that can execute their JavaScript on the server. Or the client. Or both. Razzle uses a plugin architecture that allows you to change your mind about how you build your application. It will even let you change your mind about building your code in React, Preact, or some other framework entirely, like Elm or Vue.

5 Razzle Razzle Razzle uses this method to operate with a variety of frameworks, including Angular, Preact, Vue, Svelte, and not just React. While your app is running, just type rs in the console and press Enter to restart your server.

Ya... the answer is react ssr. I like razzle but there are others.

Somehow at the interview I was asked "what i think about difficulty of configuring Webpack for Linaria, at that moment I realized, what to find a solution to set up Linaria with SSR is not simple task", but I will show you the final result for example Razzle config:

Each component is isolated and tested separately before being exported as a complete unit. It simplifies testing, because you just have to deal with this one component if you wish to make a little change. Bit is also great for test-driven development because of its component isolation.It is available for personal and open source projects at no cost. 9.Razzle Razzle simplifies SSR configuration by encapsulating it in a single dependency. It provides developers with a similar experience to create-react-app, but with more control over frameworks, routing, and data fetching.

Razzle - Build production ready React applications. Razzle is toolchain for modern static and dynamic websites and web applications

It Is Serverside Rendering Framework As Well And This Provide Much More Flexibility. Razzle Docs

Without any adding any dependencies you can connect react props to raw css at runtime with nothing but css variables (aka "custom properties"). If you add CSS modules on top you don't have to worry about affecting the global scope so components created in this way can be truly modular and transferrable. I use this with vite.

Little confused as to why it has vite in it‘s name, it seems unrelated to https://vitejs.dev/

it says in their docs that they recommend Vite https://vitejs.dev/

it goes like this.

1. you create a repo folder, you cd into it.

2. you create a client template using vite which can be plain typescript, or uses frameworks such as react or vue, at https://vitejs.dev/guide/

3. you cd in that client directory, you npm install, then you npm run dev, it should show you that it works at localhost:5173

4. you follow the instructions on your url, you do npm install @web3modal/wagmi @wagmi/core @wagmi/connectors viem

5. you follow the further instructions.

> It seems like this is for npm or yarn to pull from a remote repository maintained by @wagmi for instance. But then what?

you install the wagmi modules, then you import them in your js code, those code can run upon being loaded or upon user actions such as button clicks

> Do I just symlink to the node_modules directory somehow? Use browserify? Or these days I'd use webpack or whatever the cool kids are using these days?

no need for those. browserify is old school way of transpiling commonjs modules into browser-compatible modules. webpack is similar. vite replaces both webpack and browserify. vite also uses esbuild and swc under the hood which replaces babel.

> I totally get how node package management works ... for NODE. But all these client-side JS projects these days have docs that are clearly for the client-side but the ES2015 module examples they show seem to leave out all instructions for how to actually get the files there, as if it's obvious.

pretty much similar actually. except on client-side, you have src and dist folders. when you run "npm run build" vite will compile the src dir into dist dir. the outputs are the static files that you can serve with any http server such as npx serve, or caddy, or anything really.

> What gives? And finally, what exactly does "browserify" do these days, since I think Node supports both ES modules and and CJS modules? I also see sometimes UMD universal modules

vite supports both ecmascript modules and commonjs modules. but these days you'll just want to stick with ecmascript which makes your code consistently use import and export syntax, and you get the extra benefit of it working well with your vscode intellisense.

> In short, I'm a bit confused how to use package management properly with browsers in 2024: https://modern-web.dev/guides/going-buildless/es-modules/

if people want plain js there is unpkg.com and esm.sh way, but the vite route is the best for you as it's recommended and tested by the providers of your modules.

> And finally, if you answer this, can you spare a word about typescript? Do we still need to use Babel and Webpack together to transpile it to JS, and minify and tree-shake, or what?

I recommend typescript, as it gives you better type-safety and better intellisense, but it really depends. If you're new to it, it can slow you down at first. But as your project grows you'll eventually see the value of it. In vite there are options to scaffold your project in pure js or ts.

First you have to know that all those react projects are created using Vite, and for each of them, you need change the vite.config.ts file by adding the following configuration:

CSSHooks works with React, Prereact, Solid.js, and Qwik, and we’re going to use Vite with the React configuration. First, let's create a project called css-hooks and install Vite:

JavaScript React Flowbite Tailwind Firebase - Auth, Database, and Hosting Vite

For this full-stack single-page app, you'll use Vite.js as your frontend build tool and the react-beautiful-dnd package for draggable items.

Vite

Imagine a shiny new React app — that’s what we’ll build! We’ll use a cool tool called Vite to set it up.

Vite is a blazing fast build tool that significantly improves the development experience for React applications. It leverages modern browser features such as native ES module imports to provide near-instantaneous development server startup and rapid hot module replacement (HMR) updates. This makes the development process incredibly smooth and efficient, especially for large-scale projects.