What is React Static?

Overview of progressive static-site framework for React
16 October 2017   2770

React Static is a framework designed to help everyone painlessly build next generation, high-performance websites for the web.

With react-static you can deliver an amazing experience for your users and developers alike, without compromising React in any way. It’s insanely fast, touts fantastic SEO capabilities, and is probably the most React-friendly static-site library on the internet.

How does React Static work?

React Static framework architecture
React Static framework architecture 

Main advantages

  • Painless development & migration. There are very few differences (or changes to be made, if migrating) when compared to apps created with create-react-app, or any other standard react build system. And, if you’re already using React-Router, you likely won’t have to change anything at all!
  • Redux, Lifecycle Security, Route Animations & more! react-staticdoesn’t use any strange routing techniques or custom lifecycle methods, which means there is absolutely no dangerouslySetInnerHTMLReactDOM.render(), or any other destructive methods being used for navigation. It’s just good old React, so you can thoroughly rely on everything functioning how you would normally expect it to, including component lifecycles and state managers.
  • Data & Query Agnostic. You’ve worked hard enough producing and organizing all of the data for your website, so the last thing you need is some superfluous GraphQL layer or custom component lifecycle lodging itself between your data and your pages. With react-static, supplying and using your data is as simple. Fetch it at build time, supply it to your routes, and use the getRouteProps HOC. It’s heavenly, and it also makes testing your data and your components a breeze.
  • Lean builds for today and 2 years from now. react-static’s approach to code-splitting ensures your page data is optimized and stored separately from your JS bundle as JSON files. This means the main JS bundle will not grow in size with the amount of content on your site. Not only does this significantly improve build times for sites small and large, but also decreases the amount of duplicate code required to be downloaded by the client. All of this means faster browsing for your users, and more productivity for the developer.

See GitHub to learn more.  

Frontend News Digest 14 - 20.09

20 September 2019   140

Greetings! I hope your week went great! Here's new Frontend news digest.

In this digest, beginners can learn about CSS Grid, skilled coders may learn about, for example, what's new in Chrome 77 for developers, difference between axion and fetch() API and many other stuff.

Guides

Good overview on grips with Grid.

  • How to Easily Reuse Components Across Projects and Repositories

A tutorial on building, collaborating and distributing over components to create different projects.

  • Preview your Vue or React components using JSDoc

Guide on creating and publishing your Vue app documents

Article

It’ll only be a couple of years before we reach Chrome 100 and it seems Firefox wants a piece of the action :-) Firefox’s release cadence will be moving from approx 6-8 weeks per version to just 4 from Firefox 71 onward.

Chrome 77 is rolling out to users now. Here, Pete LePage dives in to what’s new for developers in this latest version.

  • Javascript Overcomes Java as The Most Popular Programming Language of 2019

Well, cool news for all frontenders, is suppose =)

  • CSV & Excel to JSON in JavaScript

Ajax & Fetch can help you with that, learn how exactly.

  • Source-maps could be revealing your private project files

Article on a possible vulnerability, beware!

  • Axios or fetch(): Which should you use?

Article, which is written to give you the better understanding of both APIs.