Bump deps after releasing 4.15.3

[compulim]

Related to #4388.

Changelog Entry

Changed

• Bumped all dependencies to the latest versions, by @compulim in PR #4392
  • Production dependencies
    • @babel/runtime@7.18.9
    • @emotion/css@11.10.0
    • core-js@3.24.1
    • markdown-it-attrs@4.1.4
    • markdown-it@13.0.1
    • redux@4.2.0
    • sanitize-html@2.7.1
  • Development dependencies
    • @babel/cli@7.18.10
    • @babel/core@7.18.10
    • @babel/plugin-proposal-class-properties@7.18.6
    • @babel/plugin-proposal-object-rest-spread@7.18.9
    • @babel/plugin-transform-runtime@7.18.10
    • @babel/plugin-transform-typescript@7.18.12
    • @babel/preset-env@7.18.10
    • @babel/preset-react@7.18.6
    • @babel/preset-typescript@7.18.6
    • @babel/runtime@7.18.9
    • @emotion/react@11.10.0
    • @fluentui/react@8.87.1
    • @types/node@18.7.1
    • @types/react@18.0.17
    • @typescript-eslint/eslint-plugin@5.33.0
    • @typescript-eslint/parser@5.33.0
    • babel-jest@28.1.3
    • babel-loader@8.2.5
    • babel-plugin-transform-inline-environment-variables@0.4.4
    • concurrently@7.3.0
    • core-js@3.24.1
    • dotenv@16.0.1
    • error-stack-parser@2.1.4
    • esbuild@0.15.1
    • eslint-plugin-prettier@4.2.1
    • eslint-plugin-react-hooks@4.6.0
    • eslint-plugin-react@7.30.1
    • eslint-plugin-security@1.5.0
    • eslint@8.21.0
    • express@4.18.1
    • http-proxy-middleware@2.0.6
    • husky@8.0.1
    • jest-environment-node@28.1.3
    • jest-image-snapshot@5.1.0
    • jest-junit@14.0.0
    • jest-trx-results-processor@3.0.1
    • jest@28.1.3
    • lerna@5.4.0
    • lint-staged@13.0.3
    • node-dev@7.4.3
    • nodemon@2.0.19
    • nopt@6.0.0
    • prettier@2.7.1
    • react-scripts@5.0.1
    • selenium-webdriver@4.4.0
    • serve@14.0.1
    • source-map-loader@4.0.0
    • strip-ansi@7.0.1
    • terser-webpack-plugin@5.3.3
    • typescript@4.7.4
    • webpack-cli@4.10.0
    • webpack@5.74.0

Description

Bump dependencies after releasing 4.15.3.

Update to TypeScript triggered some errors which were previously green. The errors are legit and we need fix some typings in our code instead.

Skip-bump react-redux as 8.0.2 is not ES5.

Design

Jest 28 with jest-environment-jsdom and ESM

Most package developers are aware that "package consumed in browser" means "package will be processed by Webpack/ESBuild/Rollup/etc." That means, it is okay to use either CommonJS or ESM for module resolution.

ESM is preferred because it could potentially provide better treeshaking.

Thus, many packages export itself as ESM when the consumer is a browser, i.e. via package.json/exports/./default. For example, uuid is a package which export itself as ES5 + ESM when the consumer is a browser.

When jest-environment-jsdom resolves a package, it pretend to be a browser. That means, packages resolved under jest-environment-jsdom test environment could be ESM, because the package expose ESM for browser.

As jest@28 does not support ESM yet (behind experimental flag), that means, using default configuration, packages resolved by jest-environment-jsdom could be in ESM and Jest will not be able to execute them.

Quick thinking, there are a few ways to solve the issue:

1. Enable ESM even though it is experimental
2. Use testEnvironmentOptions with { "customExportConditions": ["node"] } to resolve imports as "node" condition, which is "more likely" to be CommonJS
3. Modify transformIgnorePattern to whitelist packages that need to be transformed

We are using point 3 because:

• We don't have a lot of dependencies that export themselves as ESM under browser condition

Specific Changes

• Run npm run bump on all packages
• Correct typings in some .ts/.tsx
• Add jest-environment-jsdom as it is no longer included in jest@28
• Add react-redux to skipBump as its 8.0.1 is not a ES5 package

• I have added tests and executed them locally
• I have updated CHANGELOG.md
• I have updated documentation

Review Checklist

This section is for contributors to review your work.

• Accessibility reviewed (tab order, content readability, alt text, color contrast)
• Browser and platform compatibilities reviewed
• CSS styles reviewed (minimal rules, no z-index)
• Documents reviewed (docs, samples, live demo)
• Internationalization reviewed (strings, unit formatting)
• package.json and package-lock.json reviewed
• Security reviewed (no data URIs, check for nonce leak)
• Tests reviewed (coverage, legitimacy)