Update Shared components packages to v5 (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
typescript (source)	4.9.5 -> 5.0.2
webpack-cli (source)	4.10.0 -> 5.0.1

---

Release Notes

Microsoft/TypeScript

v5.0.2: TypeScript 5.0

Compare Source

For release notes, check out the release announcement.

For new features, check out the What's new in TypeScript v5.0.2.

For the complete list of fixed issues, check out the

• fixed issues query for Typescript v5.0.0 (Beta).
• fixed issues query for Typescript v5.0.1 (RC).
• fixed issues query for Typescript v5.0.2 (Stable).

Downloads are available on:

• npm
• NuGet package

webpack/webpack-cli

v5.0.1

Compare Source

Bug Fixes

• make define-process-env-node-env alias node-env (#​3514) (346a518)

v5.0.0

Compare Source

Bug Fixes

• improve description of the --disable-interpret option (#​3364) (bdb7e20)
• remove the redundant utils export (#​3343) (a9ce5d0)
• respect NODE_PATH env variable (#​3411) (83d1f58)
• show all CLI specific flags in the minimum help output (#​3354) (35843e8)

Features

• failOnWarnings option (#​3317) (c48c848)
• update commander to v9 (#​3460) (6621c02)
• added the --define-process-env-node-env option
• update interpret to v3 and rechoir to v0.8
• add an option for preventing interpret (#​3329) (c737383)

BREAKING CHANGES

• the minimum supported webpack version is v5.0.0 (#​3342) (b1af0dc), closes #​3342
• webpack-cli no longer supports webpack v4, the minimum supported version is webpack v5.0.0
• webpack-cli no longer supports webpack-dev-server v3, the minimum supported version is webpack-dev-server v4.0.0
• remove the migrate command (#​3291) (56b43e4), closes #​3291
• remove the --prefetch option in favor the PrefetchPlugin plugin
• remove the --node-env option in favor --define-process-env-node-env
• remove the --hot option in favor of directly using the HotModuleReplacement plugin (only for build command, for serve it will work)
• the behavior logic of the --entry option has been changed - previously it replaced your entries, now the option adds a specified entry, if you want to return the previous behavior please use webpack --entry-reset --entry './src/my-entry.js'

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   dev webpack-cli@"5.0.1" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN node_modules/@webpack-cli/configtest
npm WARN   @webpack-cli/configtest@"^1.2.0" from [email protected]
npm WARN   node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN   node_modules/@webpack-cli/configtest
npm WARN     @webpack-cli/configtest@"^1.2.0" from [email protected]
npm WARN     node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   dev webpack-cli@"5.0.1" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN node_modules/@webpack-cli/info
npm WARN   @webpack-cli/info@"^1.5.0" from [email protected]
npm WARN   node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN   node_modules/@webpack-cli/info
npm WARN     @webpack-cli/info@"^1.5.0" from [email protected]
npm WARN     node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @webpack-cli/[email protected]
npm WARN Found: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   dev webpack-cli@"5.0.1" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN node_modules/@webpack-cli/serve
npm WARN   @webpack-cli/serve@"^1.7.0" from [email protected]
npm WARN   node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm WARN 
npm WARN Conflicting peer dependency: [email protected]
npm WARN node_modules/webpack-cli
npm WARN   peer webpack-cli@"4.x.x" from @webpack-cli/[email protected]
npm WARN   node_modules/@webpack-cli/serve
npm WARN     @webpack-cli/serve@"^1.7.0" from [email protected]
npm WARN     node_modules/@redhat-cloud-services/frontend-components-config/node_modules/webpack-cli
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.2
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.2>
npm notice Run `npm install -g [email protected]` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/typescript
npm ERR!   dev typescript@"5.0.2" from the root project
npm ERR!   peer typescript@"*" from [email protected]
npm ERR!   node_modules/@redhat-cloud-services/frontend-components-config/node_modules/ts-loader
npm ERR!     ts-loader@"^8.4.0" from @redhat-cloud-services/[email protected]
npm ERR!     node_modules/@redhat-cloud-services/frontend-components-config
npm ERR!       dev @redhat-cloud-services/frontend-components-config@"4.7.0" from the root project
npm ERR!   10 more (fork-ts-checker-webpack-plugin, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional typescript@">= 4.4.x <= 4.9.x" from [email protected]
npm ERR! node_modules/msw
npm ERR!   dev msw@"1.1.0" from the root project
npm ERR!   optional msw@"latest" from @mswjs/[email protected]
npm ERR!   node_modules/@mswjs/data
npm ERR!     dev @mswjs/data@"0.11.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/typescript
npm ERR!   peerOptional typescript@">= 4.4.x <= 4.9.x" from [email protected]
npm ERR!   node_modules/msw
npm ERR!     dev msw@"1.1.0" from the root project
npm ERR!     optional msw@"latest" from @mswjs/[email protected]
npm ERR!     node_modules/@mswjs/data
npm ERR!       dev @mswjs/data@"0.11.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-20T11_07_48_044Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.