Welcome to this new npm monthly! It covers a bit more than the last month as we took a summer break from these updates.
In this edition, we have a lot to share for some major npm packages used by thousands and thousands of you, dear readers!
React 16 betas & RCs
The first beta of React was released in July, followed by 4 more betas and release candidates. You can learn all the details about what’s in this new version in this GH issue.
Dan Abramov wrote a couple of blog posts introducing some of the changes. The first one about error handling changes in React 16, followed by one about DOM Attributes in React 16 published a few days ago.
I highly encourage you to have a look at the GitHub issue here to learn about what it will mean for you and your apps.
Webpack 3.0 to 3.5.6!
The webpack team is moving fast. Since out last edition before the summer break, they released 3.0, then 3.1, 3.2, 3.3, 3.4, 3.5 and all the way up to 3.5.6. 3.2 only had bugfixes according to the changelog, but all the other 3.x had at least one feature with some bug fixes.
There is an official blog post about webpack 3 that talks about scope hoisting, “magic comments”, and more.
A new major version the popular debug package…that comes with shiny new colors! :) It also has a variety of major and minor changes all detailed in the changelog here.
Sinon.JS 3.0, 3.1 and 3.2
They wrote a migration guide for 3.0 right here. Check it out!
babel-core 7 beta
The wildly popular Babel is getting closer to releasing 7.0. It’s been in alpha for months, now they released the first beta. From what we have found in one of their milestone for Babel 7 beta, here’s what’s in it:
Dropping Node 0.10 / 0.12 / 5 support + old packages/proposals. Fix stage-x/proposal versioning (easier to align with TC39). Match Flow AST where possible. Any better defaults + remove babel-runtime dep internally for npm 2/yarn. We are using the 7.0 branch.
There is a blog post on their site about upgrading, dating from March so this might be a good place to start for upgrades. Given it’s been 6 months since it was published, it’s possibly not 100% accurate anymore.
See you next month!
In the meantime, if you think we’ve missed something, let us know.