CRA is not downloading the latest version of webpack

[brinster-Aman]

Describe the bug

I tried creating a new app using create-react-app, which in turn installed react-scripts 4.0.3, which in turn installed webpack 4.44.2. But while navigating to github repo of react-scripts, I found it uses webpack 5.41.1 link. Basically, it is not installing the latest version of nested dependencies.

Environment

current version of create-react-app: 4.0.3
running from C:\Users\223015921\AppData\Roaming\npm-cache_npx\20060\node_modules\create-react-app

System:
OS: Windows 10 10.0.18363
CPU: (8) x64 Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 93.0.4577.63
Edge: Spartan (44.18362.1533.0)
Internet Explorer: 11.0.18362.1
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: 4.0.3 => 4.0.3
npmGlobalPackages:
create-react-app: Not Found

Steps to reproduce

1. Open cmd terminal.
2. Create new react app using npx create-react-app <app-name>.
3. Check for webpack version installed.

Expected behavior

It should have installed the mentioned version of nested dependencies.

Actual behavior

Installing different version of nested dependencies rather than mentioned version.

[nrayburn-tech]

The released version, 4.0.3 uses webpack 4.44.2. This is what you are installing with npx create-react-app. The current github branch, which has not been released for use, uses the 5.x version.
When a new release is made with the 5.x version of webpack, you will be able to update and use it.

[brinster-Aman]

thanks @nrayburn-tech for this piece of information. Is there any release date plan or any expected timeline by when we can expect this release, the one which uses webpack 5.x version?

[nrayburn-tech]

I don’t maintain the library and I haven’t seen any planned release date from the maintainers.

This project is maintained by volunteers, so it is very highly dependent on the amount of free time they have and how many changes they have left before 5.0 is ready.

[stale]

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.