u/tmbtech

You can also use patch-package or yarn patch to patch node_modules. It's pretty safe because the patch is version dependent. I guess it just depends on what you mean by "work around"

Looks good! How many hours did you let it bloom for?

Oh another thing to try. Check to make sure your IDE plugin is pointed to the correct eslint version. I usually point my plugin to the node modules, but I explicitly have to set it. Otherwise it tries to get it from the global installed version or the version that is bundled with the plugin.

Are your local deps out of sync with the ci? What happens when you delete the node_modules and re-yarn the project?

follow-up question (I'm mobile) and couldn't tell from the logs - in the pipeline is it running yarn install --frozen-lockfile

AWS Amplify. https://docs.amplify.aws/

NFL mobile and the NFL fantasy app

We moved to React about 2 years ago. The actual homepage re-design has been in the works for a while. Probably more than a year (design, user testing, etc). Software development for 6 months plus source: On the front end dev team.

Black magic!

If I'm reading it correctly - You're basically queueing things up by type. Say type A -> B -> C is in the queue. A hasn't been processed yet but will be on the next tick. If another A type get queued before the tick happens it'll jump the line and get processed with the other A.

If you're on an Android phone, in chrome, you can "request desktop site". The experience isn't the best but you can import transactions then flip back to the mobile app to update your budget.

I know your asking about a promise chain, but why not use async/await instead?

const foobar = async () => {
    try{
        const item1 = await getItem1();
        const item2 = await getItem2(item1);
        const item3 = await getItem3(item1, item2);
        console.log(item3);
    } catch (e) {
       console.error(e);
    }
}

http://i.qkme.me/3prn10.jpg

This is a great breakdown. Drawing on the screen really helps drive the point home.

• https://github.com/matthew-andrews/isomorphic-fetch (server / client)
• https://github.com/github/fetch (client only)

https://github.com/nfl/react-helmet

Put some TP or one of those toilet sheets in the bowl before you go. Aka poop deck or gift wrap. http://www.urbandictionary.com/define.php?term=poop+deck&defid=7066879

Check out this project. It's a pretty good demo of a single page app with SSR.

When you render server side you call React.renderToString() which writes out html with react ids, then you send that response to the browser. On the client side you will call React.render() this is the bootstrapping process. Now your app just continues as normal.

React Starter Kit

1. Yes everything needs to be SSR in order to be indexed by the search engines. If you are curious, curl your webpage and you will see what the search engines see.
2. In short No. React will bootstrap the app and see that the DOM doesn't need to get updated and will just add the event handlers.

React.renderToString

Milk thistle. I usually take it after drinking. Don't take to much otherwise you will have mega beer shits. YMMV

If you are going to use a flux like arch, checkout refluxjs, it's really easy to get started.

Try posting in r/reactjs

I like this starter kit. https://github.com/webpack/react-starter