Update Rollup and related plugins to their most recent versions

[0xdevalias]

Summary

Update Rollup and related plugins to their most recent versions + resolve any breaking changes/deprecations/etc along the way. I made each change piece by piece, so the commit history tells a pretty good story of what was changed where/how/why.

fixes #24894

For the full deepdive/context, see:

• #24894

The inspiration for this came from @jasonwilliams 's PR for attempting to add sourcemap output support to React's builds:

• #20186
  • #21946

But I figured that it would be useful to minimise the scope of changes in that PR, and to modernise the build tooling along the way.

If any of these updates rely on a node version later than 10.x, then the following PR may have to land first, otherwise things might break on AppVeyor:

• #24891
  • #24892

How did you test this change?

See some of my testing notes RE: figuring compatible package versions + their associated changes in #24894 (comment) Of particular note is the difference in the react.development.js output between Rollup 1.x and rollup 2.x:

I'm not currently sure if these changes are significant/change the semantics of the output, or are just a different way of the bundler working, but I did notice that it increases the output file sizes a bit (most dramatically in react.development.js):

I ran the tests with yarn test --prod, and opened a separate issue for the few tests that seem to fail on Node 16.x:

• #24915

⇒  yarn test --prod

..snip..

Test Suites: 3 failed, 2 skipped, 283 passed, 286 of 288 total
Tests:       3 failed, 89 skipped, 7553 passed, 7645 total
Snapshots:   125 passed, 125 total
Time:        245.388 s
Ran all test suites.

I'm not 100% certain if this is the most thorough/complete way to test things, so I am definitely open to suggestions on how to improve confidence in these changes.

[0xdevalias]

Added a few comments/pointers to help explain some of the changes made + point to relevent docs/changelog/etc.

It's definitely also worth looking at the commits, as I tried to keep all of the changes neatly isolated, so it may help tell the story of the changes better:

• https://github.com/facebook/react/pull/24916/commits

[0xdevalias]

Added as per advice in https://github.com/rollup/plugins/blob/master/packages/babel/CHANGELOG.md#500

Removed externalHelpers & runtimeHelpers options. There is now a single babelHelpers option which can take one of 'bundled', 'inline', 'runtime' and 'external' as a value. The default is 'bundled' which matches 4.x behavior, but it is recommended to configure this option explicitly.

[0xdevalias]

TODO: options.skip was removed in @rollup/plugin-node-resolve 3.0.0

• https://github.com/rollup/plugins/blob/master/packages/node-resolve/CHANGELOG.md#300
  • rollup/rollup-plugin-node-resolve#90

Is there a different value we should be using here now in it's place? (external?)

• https://github.com/rollup/plugins/tree/master/packages/node-resolve#resolving-built-ins-like-fs

[0xdevalias]

• https://github.com/rollup/plugins/tree/master/packages/replace#preventassignment
• https://github.com/rollup/plugins/tree/master/packages/replace#values

[0xdevalias]

• https://github.com/rollup/rollup/blob/master/CHANGELOG.md#200

  • The treeshake.pureExternalModules option will now show a deprecation warning when used: use treeshake.moduleSideEffects: 'no-external' instead

• https://rollupjs.org/guide/en/#treeshakepureexternalmodules

[0xdevalias]

• https://github.com/rollup/plugins/blob/master/packages/babel/CHANGELOG.md#500

  • Removed externalHelpers & runtimeHelpers options. There is now a single babelHelpers option which can take one of 'bundled', 'inline', 'runtime' and 'external' as a value. The default is 'bundled' which matches 4.x behavior, but it is recommended to configure this option explicitly.

• https://github.com/rollup/plugins/tree/master/packages/babel#babelhelpers

[0xdevalias]

The build is currently failing due to the following error:

 BUILDING  react-server-dom-webpack-writer.browser.production.min.server.js (umd_prod)

Could not resolve import "react-server-dom-webpack/src/ReactFlightServerWebpackBundlerConfig" in /home/circleci/project/packages/react-server/src/forks/ReactFlightServerConfig.dom-browser.js using exports defined in /home/circleci/project/packages/react-server-dom-webpack/package.json.

internal/fs/utils.js:314
    throw err;
    ^

Error: ENOENT: no such file or directory, stat 'build/node_modules/react/package.json'
    at Object.statSync (fs.js:1127:3)
    at updatePackageVersions (/home/circleci/project/scripts/rollup/build-all-release-channels.js:261:22)
    at processStable (/home/circleci/project/scripts/rollup/build-all-release-channels.js:127:5)
    at Object.<anonymous> (/home/circleci/project/scripts/rollup/build-all-release-channels.js:66:5)
    at Module._compile (internal/modules/cjs/loader.js:1072:14)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
    at Module.load (internal/modules/cjs/loader.js:937:32)
    at Function.Module._load (internal/modules/cjs/loader.js:778:12)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:76:12)
    at internal/main/run_main_module.js:17:47 {
  errno: -2,
  syscall: 'stat',
  code: 'ENOENT',
  path: 'build/node_modules/react/package.json'
}

I wonder if there could be some node_modules cache weirdness happening maybe?