tinking
DISCONTINUED
rendertron
DISCONTINUED
Our great sponsors
tinking | rendertron | |
---|---|---|
4 | 15 | |
408 | 5,868 | |
- | - | |
1.8 | 0.0 | |
almost 3 years ago | over 1 year ago | |
TypeScript | TypeScript | |
GNU General Public License v3.0 only | Apache License 2.0 |
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.
tinking
We haven't tracked posts mentioning tinking yet.
Tracking mentions began in Dec 2020.
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.
[Rendertron](https://github.com/GoogleChrome/rendertron) appears to be deprecated and no longer recommended by Google. They are now recommended basically what this article is about.
-
How do I implement server side rendering in a React.js app?
GoogleChrome/Rendertron proxy https://github.com/GoogleChrome/rendertron.
- The balance has shifted away from SPAs
-
Universal worth it solely for SEO?
Rendertron, quite old now.
-
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).
-
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.
View on GitHub
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.
puppeteer-cluster - Puppeteer Pool, run a cluster of instances in parallel
puppeteer - Node.js API for Chrome
puppeteer - Headless Chrome Node.js API [Moved to: https://github.com/puppeteer/puppeteer]
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.
Scully - The Static Site Generator for Angular apps
react-native-media-query - Media queries for react-native and react-native-web
pl0t - PL0T and See the Data | Charts, Tables, Text, Formulas
ing-au-login - Login to your ING Australia bank account using puppeteer
dripsy - 🍷 Responsive, unstyled UI primitives for React Native + Web.
detect-responsive-traits - Determine responsive traits to only server-side render markup truly needed.
classless-css - A list of classless CSS themes/frameworks with screenshots