Replies: 51 comments 127 replies
-
I got this error on my app. reproduction
|
Beta Was this translation helpful? Give feedback.
-
@mrmckeb I tried it, but got same result 🤣 |
Beta Was this translation helpful? Give feedback.
-
@raix thanks guiding me. First try only apply
And then worked
Second try with both resolution lock by
After that
For testing this iteration in the CRA repository, I'll submit 100% no mock E2E test PR, that add this my app(using v4.0.3 react-scripts) source code as fixture, and make Github action process following tasks.
Off course I'll push PR several our ago from now. |
Beta Was this translation helpful? Give feedback.
-
@raix Thank you, finally worked correctly
I see, let you try |
Beta Was this translation helpful? Give feedback.
-
I got the same issue with workbox-webpack-plugin failing. I can also confirm this worked for me as well: "resolutions": {
"workbox-webpack-plugin": "6.2.0"
}, |
Beta Was this translation helpful? Give feedback.
-
It cannot work with new webpack.container.ModuleFederationPlugin({
name: "external",
filename: "remoteEntry.js",
exposes: {
"./App": "./src/App",
},
};
), |
Beta Was this translation helpful? Give feedback.
-
Tried using CRA@next this morning. Seems to be experiencing some ESLinting issues currently
Package.json
|
Beta Was this translation helpful? Give feedback.
-
Hello! Great work! I got it working, however with some issues and workarounds. Like you said before:
The major issue I have right know is with sourcemaps:
Looks like it doesn't take into account that the path is relative or something like that.
|
Beta Was this translation helpful? Give feedback.
-
Webpack 5 support? Might need to fix this first: |
Beta Was this translation helpful? Give feedback.
-
Has anyone been able to get this to work with Storybook? I believe storybook needs webpack 4. |
Beta Was this translation helpful? Give feedback.
-
Do we have a date for releasing next alpha? It'd be helpful to get rid of "resolutions" and better webpack-dev-server. |
Beta Was this translation helpful? Give feedback.
-
📣 We've released a new alpha version with the following changes:
In addition to these upgrades we've also changed the way we determine if we should use npm or Yarn when creating a new app. Previously this behaviour was non-deterministic. If someone had Yarn installed we would use Yarn and if they didn't we would use npm. Now we detect how you've invoked For example: # this will use npm
npx create-react-app my-app # both of these will use Yarn (depending which version you have installed)
yarn dlx create-react-app my-app
yarn create react-app my-app |
Beta Was this translation helpful? Give feedback.
-
Is there (or will there be) a way to configure fallbacks for node builtins without needing to eject?
|
Beta Was this translation helpful? Give feedback.
-
I've tried to start CRA with typescript and got following error Error: Module Error (from ./node_modules/postcss-loader/dist/cjs.js):
(@/home/andrei/Projects/my-ts-app/src/App.css) Error: Module Error (from ./node_modules/postcss-loader/dist/cjs.js):
(@/home/andrei/Projects/my-ts-app/src/index.css)` |
Beta Was this translation helpful? Give feedback.
-
I'm completely unable to run an app with this new version. I've tried a myriad of installation steps, but the cleanest reproduction I got is this:
Full log of errors, truncated file paths for readability
I don't know if the first 8 steps are necessary, but when I try running |
Beta Was this translation helpful? Give feedback.
-
I'm trying to upgrade my current react project so I can use the new Tailwind CSS 3.0 and PostCSS 8.0 because I want to try Tailwind's new colored shadows, but I've run into a lot of errors. I've managed to install Tailwind CSS 3.0 and PostCSS 8.0 as well as react-scripts 5.0.0. Here's my package.json:
but when I try to run yarn start, I get this error:
|
Beta Was this translation helpful? Give feedback.
-
It says next not found. Is there a package I need for the new alpha? |
Beta Was this translation helpful? Give feedback.
-
I managed to get my entire project working with
Some weird things that I still have to figure out:
|
Beta Was this translation helpful? Give feedback.
-
This looks very promising! Is there an ETA for an official release? Long time since last official update and there are a lot of deprecated/vulnerable package dependencies in the current official version. |
Beta Was this translation helpful? Give feedback.
-
So glad to see it released |
Beta Was this translation helpful? Give feedback.
-
Thank you all for your contribution.
|
Beta Was this translation helpful? Give feedback.
-
Was the removal of the runtime error overlay intentional? It was a nice feature. |
Beta Was this translation helpful? Give feedback.
-
splitChunks config was removed as part of the upgrade from webpack v4 to v5, it seems. See https://webpack.js.org/plugins/split-chunks-plugin/ . |
Beta Was this translation helpful? Give feedback.
-
Just ran the upgrade on a couple of my projects and everything worked like a charm 👌 Thank you for all the efforts in getting this released! |
Beta Was this translation helpful? Give feedback.
-
After installing latest version of React.js . I get hese assets line(see below). But when I change current react-scripts version 5.0.0 -> 4.0.3 , then run 'npm start' it work without showing assets lines. How I fix it........?????? .Please help, as a Fresher I have limited community support. "react-scripts": "5.0.0" yuvra@LAPTOP-5GI5GIT2 MINGW64 ~/Desktop/my-app (master)
Starting the development server... Compiled successfully! You can now view my-newapp in the browser. Local: http://lotcalhost:3000 Note that the development build is not optimized. assets by path static/ 1.52 MiB older "react-scripts": "4.0.3" yuvra@LAPTOP-5GI5GIT2 MINGW64 ~/Desktop/my-newapp (master)
i 「wds」: Project is running at http://192.168.255.149/ Compiled successfully! You can now view my-newapp in the browser. Local: http://localhost:3000 Note that the development build is not optimized. |
Beta Was this translation helpful? Give feedback.
-
@raix So testing on a pretty large project, apart from splitChunks (blocker) and ignoreWarnings (for source maps, hundreds of warning, annoyance), things look pretty good to me. Kudos for the work! My 2 changes to webpack.config.js:
|
Beta Was this translation helpful? Give feedback.
-
Hi All, I have updated my package in the React Application to react-script@5.0.0 On npm start, the application is working but while creating the build, it is throwing the following error. Output:- static/css/main.c713e34d.css from Css Minimizer plugin Any ways to resolve this issue? |
Beta Was this translation helpful? Give feedback.
-
are those issues being addressed? it's been 3 months since v5 was released and it seems issues are just accumulating waiting triage. I can't upgrade to tailwindcss v3 because CRA5 seems pretty broken right now. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
We've just published the first alpha release of Create React App 5 with webpack 5 support. Thanks to @raix for all his work on the webpack 5 upgrade as well as all the other contributors. 🙌
Please test this alpha release and report any issues. This is an early alpha so expect further changes in future releases.
To try the alpha follow these instructions:
JavaScript Template
TypeScript Template
Update Existing App
To update an existing app you can change the
react-scripts
version inpackage.json
tonext
and then runyarn
ornpm install
Changes
You can see a list of all the changes in this release here: https://github.com/facebook/create-react-app/milestone/81?closed=1
Beta Was this translation helpful? Give feedback.
All reactions