Modular JavaScript is an open effort to improve our collective understanding of writing robust, well-tested, and modular applications. The series consists of five books, each of which explores a key aspect of JavaScript development — comprehensively. The books are produced in the open: anyone can track their progress, report issues & contribute fixes or content. A free-to-read version is available online! Digital & print books can be purchased through O’Reilly Media. The crowdfunding campaign is on Indiegogo! 
It’s already over 100% funded! |  |
|
This step-by-step guide will teach you how to implicitly Code Split your React application using React Router and Webpack 2. |  |
|
I want to learn React… but what should I build? |
|
Wallaby.js provides instant feedback from your tests and realtime code coverage right in your editor, no more context switching. Now with test analytics and coverage reports.  |  |
|
Kent gives his reasoning for migrating from Mocha to Jest, and explains the problems he ran into across the way. |
|
Preact recreates the core value proposition of React using as little code as possible, with first-class support for ES2015. The library is currently around 3kB (minified & gzipped). |
|
We all recognize emoji. They’ve become the global pop stars of digital communication. But what are they, technically speaking? And what might we learn by taking a closer look at these images, characters, pictographs… whatever they are  (Thinking Face). We will dig deep to learn about how these thingamajigs work. |
|
EU tech hubs face a shortage of Developers. Join Honeypot! 
Companies apply to you with salary and tech stack upfront. |  |
|
A guide to designing web experiences for slow networks and offline. |
|
I’ve always loved 3D geometry. Which has meant getting drawn towards playing with CSS 3D transforms in order to create various geometric shapes. I’ve often been asked whether it would be possible to create responsive 3D shapes. I thought it would be a good idea to put the response in an article. Let’s dive in! |  |
|
I recently wrote about how to create a good pull request, this is, how to make your code changes easy to review and discuss. Now we’re going to talk about the second part: reviewing someone else’s code. This puts you on the reviewers side, and hopefully the person submitting code did follow our guidelines to make your life easier. There are several approaches you can take to review the code, but we’re going to enumerate a checklist that you could use to minimize the usage of your time and the efficiency of the code review. |
|
What are the properties that make the web the web? How can we keep differentiating from native to stay relevant in a mobile world? |
|
Postulating that there might be bots, build systems or other researchers mass downloading and running modules from npm; Adam figured it might be an interesting vector to attack systems and gain a foothold for some org and was curious to know what that traffic looked like. |
|
In 2016, there are 42 billion devices connected worldwide. Glasses, gates, clocks, padlocks, connected thermostats and many others are now part of our everyday environment. Today, the only way to access their functionality is to develop a specific application (mobile, web) for each single object — but this solution cannot scale to the amazing growth of connected devices. |  |
|
I like Web Components. It has taken a long time to get here but things are moving in the correct direction with Safari shipping Shadow DOM and now landing support for Custom Elements. |
|
|
Modular JavaScript book series is being crowdfunded!
Comments