Addresses issues with pollution and build.

Addresses issues with reuse and standarization.

Addresses issues with shims, promise libraries.

http://es6-features.org/

https://gist.github.com/staltz/868e7e9bc2a7b8c1f754

https://www.smashingmagazine.com/2011/01/guidelines-for-responsive-web-design/

http://aspiringcraftsman.com/2012/01/22/solid-javascript-the-dependency-inversion-principle/

http://www.typescriptlang.org/

The current best practice is moving forward with the supported language at an organization by incrementally adding in additional presets associated with the Babel configuration. Minimally this covers the ES2015 features but would likely move forward to include each of the following:

• http://babeljs.io/docs/plugins/preset-es2015/
• http://babeljs.io/docs/plugins/preset-es2016/
• http://babeljs.io/docs/plugins/preset-es2017/

These are covered by using http://babeljs.io/docs/plugins/preset-latest/ but during an evaluation of the specific language features it's worth seeing the behavior without the preset.

Example: https://gist.github.com/jwalsh/217a7f96758e0e3d8357a9bc5daec5af

• Caja
• http://www.adsafe.org/

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/trim#Polyfill

http://james.padolsey.com/jquery/#v=git&fn=jQuery.ajax https://github.com/jquery/jquery/blob/master/src/ajax/jsonp.js

http://chrisawren.com/posts/Learning-Advanced-JavaScript-via-the-Backbone-js-source-code http://backbonejs.org/docs/backbone.html

https://github.com/lodash/lodash/blob/4.6.0-npm-packages/lodash.map/index.js

https://cheli.me/post/reading-react-source-code

https://www.promisejs.org/implementing/

• JDG: full reference for core or when needing a summary of expected security behavior
• Functional JavaScript: excellent summary of essential tool when working functionally particularly with arrays; nice summary of partial application and currying
• Maintainable JavaScript: may not follow the rules that are being used with React but is a great summary of patterns that people should recognize if if linting, namespace, module builders, etc. cover some of the risks
• JavaScript Design Patterns: sections on module loaders, jQuery, could be avoided but the Design Pattern and MV* sections are a good contrast
• Secrets of the JavaScript Ninja
• Even Faster Websites: classic; required for CDN and debugging
• JavaScript Enlightment
• High Performance JavaScript: some of the consideration maybe we better covered by Web Page Test, Chrome Developer Tools, or Page Speed but still a good overview
• Third-Party JavaScript: for non-UI development this covers many of the considerations for cross-domain communication, build, and testing

For dealing with the current tools and ecosystem the following are recommended since it covers the core cases of dealing with the language, transpiling, upgrading libraries, async, and reactive design.

• Nicholas Zakas, Understanding ECMAScript 6
• Kyle Simpsons, ES6 and Beyond

• Stoyan Stefanov, React Up and Running

Given the current rate of change associated with ECMAScript I've not looked too closely at the state of the following for use actively in React-driven, dashboard or visualization, or Third-Party JavaScript.

• TypeScript https://www.typescriptlang.org/
• Elm http://elm-lang.org/
• Dart https://www.dartlang.org/
• ClojureScript https://github.com/clojure/clojurescript
• CoffeeScript https://github.com/jashkenas/coffeescript/wiki/list-of-languages-that-compile-to-js

• Kyle Simpsons, Async & Performance
• Daniel Parker, JavaScript with Promises

• Mario Casciaro, Node.js Design Patterns

• Functional and Reactive Domain Modeling
• Grokking Reactive User Interfaces