The primary focus of Version 8 is to get on React version 17 and Webpack Dev Server version 4. If you are already using React V17 and are not using config overrides, you're all set and require no migration.

Configs are now retrieved from the root of the package instead of following the jsPath.

The dev-server.config.js config has been rewritten basically from scratch so you'll need to update your overrides to take into account any changes. Refer to WebPack Dev Server migration guide.

The webpack.dev.js config has been adjusted to remove the extra webpack-dev-server and webpack/hot items from the `entry. See this commit for details. If you don't remove the superfluous entries, your console log will fill with "Socket failed" errors which can be maddening to debug.

This feature has not been used for quite some time and has now been removed. If you have the regenerate_revision specified in your package.json you'll want to use an alternate approach such as a Git hook or deployment script.

This means the root and regenerate_revision values in package.json are now ignored and may be removed.

For reference commit.

This package is using React V17 for all dependencies. It is recommended to update your packages/apps to support React V17 when using JS Boilerplate V8.

You'll likely need to update the following references in package.json.

1. @types/react: "^17"
2. eslint: "^8"

The Enzyme adapter has changed to the unofficial @wojtekmaj/enzyme-adapter-react-17 package. In your setup.js file change:

• Old: import Adapter from 'enzyme-adapter-react-16';
• New: import Adapter from '@wojtekmaj/enzyme-adapter-react-17';

The following warnings will likely occur when running yarn install and are not of concern.

@lipemat/js-boilerplate@npm:8.0.0-beta.5 provides react (p49ccb) with version 17.0.2, which doesn't satisfy what @hot-loader/react-dom requests The package @hot-loader/react-dom is pointed to 17.0.1 but works fine with 17.0.2.

There is a issue logged to prompt the maintainer to fix.