Update all dependencies

[jd1048576]

I have attempted to update all dependencies to as new as possible, there are a few packages now that are esm only so I have incremented them to the latest available commonjs versions. I have verified my changes by running the integration tests as well as the e2e tests using github actions, the macos node 16 build failed but that seems to be the same as what is on main. I held off on updating eslint to 8 due to the the incompatibility still of the plugins with 8. I had to update the hashes for the css modules, I assume something has changed in webpack since the changes in the module itself don't look like they should affect the hash.

Edit 12 November: I have now updated eslint to 8 as all plugins now seem to be compatible (#11374), the peer dependency also had to be increased as eslint-plugin-flowtype@8 is only compatible with eslint 8. Note it probably worth looking at the config to see if any new rules should be enabled.

[GoetzGoerisch]

@jd1048576 great, could you also include the update workbox-webpack-plugin@6.4.1 to fix the JSONPOINTER vulnerability: https://security.snyk.io/vuln/SNYK-JS-JSONPOINTER-1577288

[jd1048576]

@GoetzGoerisch I have updated the pr to include workbox-webpack-plugin@6.4.1

[iansu]

Looks like a couple of tests are still failing on macOS. If we can get those fixed then I think we can merge this.

[jd1048576]

@iansu I don't think the test failures are due to the changes here, I have updated the timeout to 10 minutes for the macOS runner as it seems to have a high variability in test times resulting in jest timing out.

Here is the output from https://github.com/jd1048576/create-react-app/runs/4247435239?check_suite_focus=true

PASS test/integration/create-react-app/index.test.js (567.808 s)
create-react-app
✓ asks to supply an argument if none supplied (239 ms)
✓ creates a project on supplying a name as the argument (344465 ms)
✓ warns about conflicting files in path (5464 ms)
✓ creates a project in the current directory (53972 ms)
✓ uses yarn as the package manager (99955 ms)
✓ creates a project based on the typescript template (57753 ms)

[GoetzGoerisch]

@iansu could we please get this merged and build/publish a new 5.0.0-next version?

@jd1048576 thanks for this! 👍🏻

[raix]

@jd1048576 Thank you for the pr! We plan to get the eslint v8 in #11375 - the failing tests might be related to eslint. If you are up for it we could try removing the eslint updates from this pr to see if it would fix the tests?
cc @iansu

[jd1048576]

@raix I can attempt to remove the eslint specific updates if you want or can wait for #11375 and rebase, I don't however think the changes made hear are specific to test failures as they all passed in or the mock pr I created on my fork after I updated the timeout for the macOS github runner https://github.com/jd1048576/create-react-app/actions/runs/1507045894

[raix]

@jd1048576 seems like tests are also failing on main... let's get #11375 in first then rebase - I'm currently trying to fix the integration tests.

[iansu]

This looks great. If you can remove the ESLint upgrade then I think we can merge this.

[raix]

Tests should be fixed on main now 🤞

[jd1048576]

@iansu I have reverted eslint back to 8.3.0 after rebasing due to #11375 being merged so hopefully this pr is ok now. @raix I noticed that @svgr/webpack@6 was released since the pr was opened and I attempted to see if I can also include it here but I believe it requires a few changes to the webpack config which I could not get working easily so its probably worth doing that in a follow up pr

[MichaelDeBoey]

@iansu Seems like all tests are green, so this one can be merged too I guess

[iansu]

Thanks!

[sKopheK]

open version upgrade (7.0.2 -> 8.4.0) broke BROWSER env handling