Packages

react-dom

19.3.1 · 14 Oct 2026MIT260.6M / weekRepositoryHomepagenpmAtom feed

Upgrading react-dom From 0.14.10 to 15.0.0

1 release in betweenevery note read

Other targets from 0.14.10Latest19.3.1
  1. 0.14.10yours
  2. 15.0.0target

Before you upgrade

Tick each one off as you go
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0
  • Breaking15.0.0

Release by release

  1. 15.0.0

    Migration needed7 Apr 201621 new · 17 fixes
    • Breaking

      Initial render now uses document.createElement instead of generating HTML. Previously we would generate a large string of HTML and then set node.innerHTML. At the time, this was decided to be faster than using document.createElement for the majority of cases and browsers that we supported. Browsers have continued to improve and so overwhelmingly this is no longer true. By using createElement we can make other parts of React faster. (@spicyj in #5205)

    • Breaking

      No more extra <span>s. ReactDOM will now render plain text nodes interspersed with comment nodes that are used for demarcation. This gives us the same ability to update individual pieces of text, without creating extra nested nodes. If you were targeting these <span>s in your CSS, you will need to adjust accordingly. You can always render them explicitly in your components. (@mwiencek in #5753)

    • Breaking

      Rendering null now uses comment nodes. Previously null would render to <noscript> elements. We now use comment nodes. This may cause issues if making use of :nth-child CSS selectors. While we consider this rendering behavior an implementation detail of React, it's worth noting the potential problem. ()@spicyj in #5451)

    • Breaking

      Functional components can now return null. We added support for defining stateless components as functions in React 0.14. However, React 0.14 still allowed you to define a class component without extending React.Component or using React.createClass(), so we couldn’t reliably tell if your component is a function or a class, and did not allow returning null from it. This issue is solved in React 15, and you can now return null from any component, whether it is a class or a function. (@jimfb in #5884)

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.