We switched from publishing multiple files for each build to a single file in v5, just like React itself (we copied their code! 😉). But now all our builds pass all our tests. Before this release we were only running tests on our source code, so there was a chance that our build introduced a bug somewhere.
#React router dom version full#
Other housekeeping items in this release include a complete overhaul to our bundling infrastructure and full test coverage for all bundles we publish. Side note: we have been working on this problem for over 2 years now. Using the new context API in React 16 (we use Jamie Kyle's create-react-context shim for backwards compat with React 15) also allows us to avoid the "update blocking" problem that you may have had to work around in the past. My sincere thanks to Tim Dorr for getting the ball rolling here, and my good friend Jared Palmer for prodding me along. This includes upgrading from using React's legacy context API, as well as eliminating all other warnings. We know that a lot of React Router users are maintaing apps they've built over the last few years using various versions of React 15 or 16 and React Router 4, and we are showing our committment to you with this release. The most significant improvement in v5 is better allaround support for React 16, while maintaining full compatibility with React >= 15. 🎉 Version 5 will pick up where the 4.x roadmap (now the 5.x roadmap) left off.
#React router dom version code#
If you are already using version 4.x, you can use version 5 immediately with zero code changes. There are no breaking changes in this release. This release is light on features and fixes, and is more focused on stability and compatibility and preparing the library for future releases.
0 kommentar(er)
