React Top 10 Articles For the Past Month (v.Oct 2017)

React Top 10 Articles For the Past Month (v.Oct 2017). @reactjs #JavaScript

  • React Top 10 Articles For the Past Month (v.Oct 2017)For the past month, we’ve ranked nearly 1,200 React articles to pick the Top 10 stories that can help advance your career.
  • (0.8% chance to be picked in the list)Topics in this list: Progressive Web App, Preact, Redux, Server Side Rendering, Structure, GraphQL, AWS, Component, AnimationOpen source of the month is included at the end.Top 10 for JavaScript, Node, Angular are posted separately in the publicationMybridge AI ranks articles based on the…
  • This is a competitive list and you’ll find the experience and techniques shared by the React leaders useful.A React And Preact Progressive Web App Performance Case Study: Treebo.

For the past month, we’ve ranked nearly 1,200 React articles to pick the Top 10 stories that can help advance your career. (0.8% chance to be picked in the list)
Continue reading “React Top 10 Articles For the Past Month (v.Oct 2017)”

Architecting a Squiggle – Birchbox Unboxed

Architecting a Squiggle  #react #components #css #reactjs

  • It looked like this, and was used to visually emphasize key words or numbers in a block of text.A SquiggleWith the assumption that this coral squiggle would be used only sporadically on a few key pages, we uploaded an image of the squiggle to our CDN and set it as…
  • Our new site, which was built in React, encouraged a component based approach.I created a Squiggle component (later renamed Highlight when it supported shapes other than squiggles) that wrapped any arbitrary content.
  • It accepted props for color, type, and alignment with respect to its content.Highlight type=’wave’ fill=’coral’ alignment=’right’ {title}/HighlightThe component used react-measure to listen to the height of if its children and record it in the component state.
  • ‘wave’ : ‘none’} fill=’coral’ alignment=’right’ {title}/HighlightAn example of conditional highlighting, made possible by the ‘none’ shapeRecently one of my teammates built support for Highlight in our custom Markdown component.
  • No developer time required!This tout was built by our web production team using only Markdown in the CMSWhy I Love itHighlight is one of my favorite components in the Birchbox repository because it makes highlighting text on our site as easy and therapeutically pleasing as highlighting text on a physical page.

When Birchbox rebranded in 2016, our new brand guide included a squiggle. It looked like this, and was used to visually emphasize key words or numbers in a block of text. With the assumption that…
Continue reading “Architecting a Squiggle – Birchbox Unboxed”

Writing Easily Testable Code with Stateless Components in React.js

Writing Easily Testable Code with Stateless Components in #React.JS  #javascript #testing

  • The use of Stateless Functional Components (a.k.a. “pure” or “dumb” components) in React.js continues to grow since first it was released in React 0.14, and for good reasons.
  • By relying on pure components, developers end up writing reusable code that’s extremely easy to test, which leads to better application architecture.
  • Personally, I like the term “pure component” because it’s indicative of what the code really is — a pure function sprinkled with some JSX.
  • In addition to these benefits, pure components also make it extremely easy to test code with any crazy props that you wish.
  • As we just saw, the code for functional components provides us awesome intel for everything we need to know in order to write effective tests.

Functional Stateless Components provides clean syntax that allows us to write more declarative code. We will look at stateless components and finish up with some unit tests in this article.
Continue reading “Writing Easily Testable Code with Stateless Components in React.js”

#React Components – Zero To Hero Series – Part 2 by Vipul Jain cc @CsharpCorner #ReactJS

#React Components - Zero To Hero Series - Part 2 by Vipul Jain cc @CsharpCorner  #ReactJS

  • This is the second article in the ReactJS – Zero to Hero Series.
  • I recommend reading the first article (link given below), before going through this article.
  • In this article, we will see the explanation of React Components.
  • Components are the fundamental units of a React application.
  • Now, with this basic understanding, in the next articles, we will see more about Populating Props, Composing components, State, Default props and Validating props.

This is the second article in ReactJS – Zero to Hero Series. I will recommend you read the first article (link given below), before going through this article.
Continue reading “#React Components – Zero To Hero Series – Part 2 by Vipul Jain cc @CsharpCorner #ReactJS”

Writing Easily Testable Code with Stateless Components in React.js

  • The use of Stateless Functional Components (a.k.a. “pure” or “dumb” components) in React.js continues to grow since first it was released in React 0.14, and for good reasons.
  • By relying on pure components, developers end up writing reusable code that’s extremely easy to test, which leads to better application architecture.
  • Personally, I like the term “pure component” because it’s indicative of what the code really is — a pure function sprinkled with some JSX.
  • In addition to these benefits, pure components also make it extremely easy to test code with any crazy props that you wish.
  • As we just saw, the code for functional components provides us awesome intel for everything we need to know in order to write effective tests.

Functional Stateless Components provides clean syntax that allows us to write more declarative code. We will look at stateless components and finish up with some unit tests in this article.
Continue reading “Writing Easily Testable Code with Stateless Components in React.js”

Day 36: Soon Come Soon – conshus – Medium

Day 36: Soon Come Soon  #hiphop #firebase #react #coding #ux #reactjs

  • Did a little bit of coding.Monday: Since I was off for Labor Day, I decided to devote the day to really getting a lot done on my refactor project.
  • I learned A LOT about what you can and can not do in React!
  • Worked out the integration of using Google Sheets as a backend to update my info section.
  • That turned out to be a lot more difficult than I thought, but I think it will be beneficial in the end.
  • I also got the audio player working the way I want.Right now, all I have to do is add the content for the thank you and tech built with sections of the info page.

Right now, all I have to do is add the content for the thank you and tech built with sections of the info page. I’m thinking I want to add a section to put my shirt shop just incase if people want to…
Continue reading “Day 36: Soon Come Soon – conshus – Medium”

Using Electrode to Improve React Server Side Render Performance By Up To 70%

  • js application platform that powers walmart.com with several goals in mind, including ease of use, re-usability of components across applications and, most importantly, performance.We use server side rendering for almost all of our applications for two reasons:Improved performance for the customerBetter for SEOIn our tests, however, we found that React’s renderToString() takes quite a while to execute — and since renderToString() is synchronous, the server is blocked while it runs.
  • Every server side render executes renderToString() to build the HTML that the application server will be sending to the browser.To solve this problem, we created two Electrode modules: Above the Fold Render (ATF) and Server Side Render Profiling and Caching (SSR Caching).
  • The average renderToString()call with this configuration took 153.80 ms.Electrode default, though, Electrode comes with renderWithIds:false, which gives us a renderToString() time of 124.80 ms. Not bad — Electrode’s default configuration has already improved render time by 19%!
  • That drops our renderToString() time all the way to 36.56 ms — an astounding 71% improvement from the default Electrode configuration, and a 76% improvement from our original, unoptimized test.
  • That means a 70% improvement won’t mean 90 ms, but 180 ms saved.Special Thanks:To Arunesh Joshi, Dmitry Yesin, and the home page team who have implemented the Electrode modules and are using them on the home page in production.To Caoyang Shi, for helping to gather data and ensuring we’re getting the right numbers!More Information:Check out Joel Chen’s post on ReactJS SSR Profiling and Caching or Arpan Nanavati’s post on Building React.js at Enterprise Scale.Check out my post about the release of Electrode, the customer-facing platform that powers Walmart.com.The Electrode website: www.electrode.io

We built Electrode, the react/node.js application platform that powers walmart.com with several goals in mind, including ease of use, re-usability of components across applications and, most…
Continue reading “Using Electrode to Improve React Server Side Render Performance By Up To 70%”