rendertron
detect-responsive-traits
Our great sponsors
rendertron | detect-responsive-traits | |
---|---|---|
15 | 2 | |
5,868 | 39 | |
- | - | |
0.0 | 5.1 | |
over 1 year ago | 3 months ago | |
TypeScript | TypeScript | |
Apache License 2.0 | 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.
rendertron
-
The Future (and the Past) of the Web Is Server Side Rendering
Rendertron is deprecated
Please note that this project is deprecated. Dynamic rendering is not a recommended approach and there are better approaches to rendering on the web.
Rendertron will not be actively maintained at this point.
https://github.com/GoogleChrome/rendertron
-
How do I implement server side rendering in a React.js app?
GoogleChrome/Rendertron proxy https://github.com/GoogleChrome/rendertron.
-
Use SSR only for search engines
Are you worried that rendertron isn't being maintained? (https://github.com/GoogleChrome/rendertron/issues/865 and https://github.com/GoogleChrome/rendertron/issues/801) Have you thought about using anything else or doing it yourself with Puppeteer or Playwright?
- The balance has shifted away from SPAs
-
Universal worth it solely for SEO?
Rendertron, quite old now.
- Rendertron – A Headless Chrome Rendering Solution
-
How to combine React Native Web + responsivity + NextJS SSR, to get SEO
Googlebot: SSR a non-responsive mobile version only for the Googlebot User Agent, to get SEO. But do Client-Side Rendering (CSR) for users, to get full responsivity. Could be done with manual user-agent sniffing, or with a GoogleChrome/Rendertron proxy. Though Google may not like being fed something different than users (different initial markup, even though resulting markup after React’s first CSR should be the same). But it might be problematic long-term to SSR only for the Googlebot, since it’s effectively serving the Googlebot something else than what the users get.. Google might crack down on it, since it could be abused.
-
Anyone tried Deno for something serious??
This might be another one: https://github.com/GoogleChrome/rendertron (not sure if it does everything that prerender does or not).
-
Next.js 11 released
Still prefer CRA with Dynamic Rendering with rendertron over Next.js and Gatsby...
-
Do you really need NextJS for SSR? 🤔
A demo Rendertron service is available at https://render-tron.appspot.com/. It is not designed to be used as a production endpoint. You can use it, but there are no uptime guarantees.
detect-responsive-traits
-
How to combine React Native Web + responsivity + NextJS SSR, to get SEO
Optimise Fresnel with detect-responsive-traits: SSR based on sniffing user-agent where it can, but all breakpoints if not. To optimise bytes sent over-the-wire.
-
Magnus UI vs. Dripsy - Chakra UI alternatives for React Native (+Web)
Before, Dripsy used a library called Fresnel to achieve achieve Responsivity with CSS media queries. CSS breakpoints on web will rely on the mobile device's user agent for most cases. But since this can be inaccurate, Fresnel also uses pre-emptive server-side breakpoint generation. Basically, if the mobile user-agent cannot be accurately detected (if you combine Fresnel with its sister library, detect-responsive-traits), then Fresnel will render all media query breakpoints on the server (a bit of extra work for the server, since it might lead to rendering more components). So the client's browser will receive all breakpoints on first render and can immediately start rendering according to the correct ones. Instead of waiting for React to rehydrate before only then running the media queries with CSS-in-JS, which would have given latency and potentially unwanted visual side-effects. This becomes most acute when you are using SSR, and thus don't want to wait for rehydration on the client to start showing the responsively laid out content.
What are some alternatives?
prerender - Node server that uses Headless Chrome to render a javascript-rendered page as HTML. To be used in conjunction with prerender middleware.
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.
puppeteer-cluster - Puppeteer Pool, run a cluster of instances in parallel
dripsy - 🍷 Responsive, unstyled UI primitives for React Native + Web.
puppeteer - Node.js API for Chrome
react-native-extended-stylesheet - Extended StyleSheets for React Native
puppeteer - Headless Chrome Node.js API [Moved to: https://github.com/puppeteer/puppeteer]
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
react-native-magnus - A Utility-First React Native UI Framework 🚀🧩
Scully - The Static Site Generator for Angular apps
react-native-media-query - Media queries for react-native and react-native-web