GraphQL for Node.js is the most exciting library of 2017. GraphQL (the QL stands for query language) is a natural evolution of APIs: it makes it easier to ask a web service questions without having to work as hard for the answers. While RESTful APIs provided a clean way to publish and present data, building APIs based on static object definitions force a lot of work on the things that need the data, which is wasteful and complex (as you end up with much more data than you need). And while including the concept of server-side queries isn’t new to APIs, GraphQL does it with a simple syntax that fits nicely into the JS world.
React had a great year as well, with a major feature release and some sweeping licensing changes. I think the combination of these changes and the vitality of the React ecosystem have pushed it well past AngularJS this year. Redux has gained a bunch of ground over Flux this year too, though Facebook could undo that in 2018 with their partial-kinda-sort-of replacement QL/Flux hybrid Relay. The next version of React Fiber has already landed in v16 and will be core to significant improvements to React applications in 2018.
One of the ways to gauge the success of a UI framework is in what gets built with it. This Fall I found a solid spreadsheet component. I’ve also been using SemanticUI and its React bindings, though I am a bit worried about their slow pace of updates. There are a few commercial UI kits, like ExtReact and Webix that have some legs, though I’d love a richer open kit that we could all contribute to.
Speaking of editors, I switched to Visual Studio Code this year, which is built on Electron (Node, Chromium, and V8). VSC replaces both Atom and Sublime, as well as my older favs Coda and Espresso. Visual Studio Code plays well with all of the recent linters, CI, build tools, and other gizmos. It performs well for coding tasks in JS and the various web formats I use regularly. When I work with larger text files, however, I’ll still switch to the Vim of Mac (TextMate), or actual Vim (though I’m getting pretty rusty with that these days).
There was a time when I couldn’t imagine Microsoft as a leader in OSS or web tech, but they’ve found their mojo with VSC and have a steady release cadence that’s downright impressive.
console.log() code. Ink also makes it easy to write more complex CLI tools, which could be especially good for the ecosystem.
In terms of packaging tools, I haven’t sided on a single bundler this year. That said, I do find webpack easy to set up and use. It’s one of the current generation of build tools, and has simpler, clearer configuration than its predecessors. ParcelJS is on my radar as a simpler way to bundle JS applications, but I haven’t had a chance to use it on anything big yet.
Storybook is one of those unexpected tools: it’s a mature UI builder for ReactJS, that feels about the way a UI builder should feel these days. I didn’t find myself getting lost in a tonne of automated code generation (i.e., it felt surprisingly lightweight). I haven’t used it in production yet, but I’m looking for ways to make it part of my prototype toolchain for early 2018.
- Another way to think about
- A very succinct ES6 cheet sheet
- Some recommended NodeJS practices
- Some async/await learning (a pending feature in ES7)
- The AirBnB JS style guidelines that pretty much everyone uses these days
- A cartoon intro to Fiber, a very detailed view at how rendering improves with fibers
- The state of JS in 2017