server-components-demo
concurrently
server-components-demo | concurrently | |
---|---|---|
11 | 6 | |
4,188 | 0 | |
0.6% | - | |
2.2 | 3.2 | |
about 2 months ago | almost 3 years ago | |
JavaScript | JavaScript | |
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.
server-components-demo
-
React Server Components Without a Framework
I, along with many ReactJS devs, have been following the development of the "new" React Server Components API with excitement. It solves some common problems in React around data fetching and efficiency in client side applications. If you're interested in learning more about the API I'd recommend you listen to the recent JS Party podcast with Dan Abramov and Joe Savona from the React Team on the future of React, and then check out the React Server Components Demo on GitHub.
-
So, why Server Components?
I borrowed this piece of code from the React Server Components demo Notes application.
-
Harnessing the power of React Server Components + Miro
And perhaps most importantly, one of the biggest limitations of RSC at this time is their out-of-the-box support. Currently, the React team has partnered with Vercel/NextJS to develop some boilerplate functionality within the NextJS structure (still experimental). Note: This boilerplate demo app was developed in the early stages of RSC, and will be replaced by the Layouts RFC going forward.
- React Server Components and Remix
-
Let's make a web application with React Server Components.
See the README for how to install the demo. https://github.com/reactjs/server-components-demo
-
React Futures - Server Components
Let’s use this example of a server component:
-
Should You Care About React Server Components?
For example, as I started to play around with the React team’s Server Components demo, I realized I had to fundamentally change how I approached building components. Instead of just creating a new file and typing export const MyComponent = () => {}, I now had to start thinking about how the component would be used, to help determine whether it was a better fit for the client or the server.
-
What are React Server Components and will you need to use them in the future?
If you want to play around with the demo code for React Server Components, you can find this code on GitHub.
-
An Introduction to React Server Components
As we see in the demo app, the server component is rendered in a special format which can be read by the client. We can see the special format in the below image
-
Yet Another Article About React Server Components
I'm looking forward to trying out React server components (I plan to fork the React team's demo and play with it), but I don't see myself having a heavy use for it in my everyday life. I'm not currently working on any personal projects that require interactivity, and for the projects I'm working on, server-side rendering is probably a better way to reduce my bundle size.
concurrently
-
React Futures - Server Components
In our demonstration, we use Webpack to build apps and Babel to transpile React code to plain JavaScript. We run our server with Express.js and use concurrently to run multiple commands concurrently. The tool nodemon helps develop node.js-based applications by automatically restarting the node application when file changes in the directory are detected.
-
Needing help: How are front-end folks setting up build processes with .NET?
It seems like you're trying to solve a developer experience, or DX, problem. I believe the "norm" is to have these scripts run separately, e.g., run npm start and dotnet watch in separate terminals. However, if you want to make it so you don't have to do that, which is fine everyone develops differently, then you could look into concurrently. Then you could add a script to the frontend's package.json like npm start to run concurrently "webpack serve" "dotnet watch".
-
npm concurrently issue
https://www.npmjs.com/package/concurrently#usage
-
Creating a monorepo containing multiple node+react applications?
Another user, /u/jamdatadude, suggested concurrently. I think this can fit your use case here!
-
MERN Stack Proxy Port - Setting a Variable for React
I’m no pro at this, but if I remember correctly, you want to build a separate server and client folder and then set up a proxy and use https://www.npmjs.com/package/concurrently
-
Landing Starter Template based on TailwindCSS, AlpineJs and build on esbuild and PostCSS
To run both commands, will use the concurrently npm package:
What are some alternatives?
react-18 - Workgroup for React 18 release.
vite - Next generation frontend tooling. It's fast!
cross-env
Tailwind CSS - A utility-first CSS framework for rapid UI development.
rfcs - RFCs for changes to React
esbuild - An extremely fast bundler for the web
react-component-compiler - React Client and Server Components without a Framework
PostCSS - Transforming styles with JS plugins
miro-workshop-finished - A finished version of the 2022 We Are Developers workshop hosted by Miro
Nodemon.io - Monitor for any changes in your node.js application and automatically restart the server - perfect for development
rfcs - RFCs for changes to React
BrunoLau.SpaServices - Port of Microsoft.AspNetCore.SpaServices into .NET 6 by using the Jering.Javascript.NodeJS interop library