Issue with react-scripts not updating for 2 years #13503
Comments
|
As far as I know, create-react-app is kind of abandoned. It's not even mentioned in the react install page anymore. For me, the easiest solution was to replace it with vite. Good luck! |
|
Hi, you can try Rsbuild as an alternative to CRA: https://github.com/web-infra-dev/rsbuild Rsbuild is a build tool powered by Rspack. Switching from CRA to Rsbuild is straightforward and can result in significant performance gains. There is a migration guide for CRA users in the Rsbuild website: https://rsbuild.dev/guide/migration/cra |
|
@1eldiego Good evening, is Create-React-App really abandoned? I'm joining now to contribute, help and network... Vite is a good alternative too, I recommend it. |
|
Yes. it's abandoned. no updates for 2 years.. not recommended by React.dev site anymore. |
- facebook/create-react-app#13503 - facebook/create-react-app#13368 Steps done (unordered): - Replace `@testing-library/react` with `react-test-renderer`. - To let `import` to work with paths relative to `src/` base, either: - Add `vite-tsconfig-paths` to `package.json`, `vite.config.ts` and `vitest.config.ts`. Add SASS config `includePaths` to `css.preprocessorOptions.scss` in `vite.config.ts`. - Change all such imports in a project to either be fully relative with `./` or `../`. - Introduce some alias like `@` for `src` in `vite.config.ts` and replace all such imports to have this prefix. - Upgrade TypeScript 4 to 5, so don't need some backward declarations. - Replace and upgrade dependencies in `package.json`, remove `node_modules/` and `package-lock.json`, then `npm i`. - Manually tweak some eslint rules for a while to focus on current task without spreading to lots of refactoring. - Output dirs `build*` became `dist` in scripts and configs to keep vite default. A `build/static` output subdir is now `dist/assets`. - `*.html` moved from `public` subdir to frontend root dir. - Remove useless not-existing `%PUBLIC_URL%` prefix from HTML. - Add main ts file into HTML. - Don't need frontend/scripts/fix-build.sh anymore to deduplicate SVG. - svgr: add `vite-plugin-svgr` to `vite.config.ts` and replace `ReactComponent` in imports with `default` and `.svg?react`. - Replace `process.env.NODE_ENV <op> "development"|"production"` with `import.meta.env.PROD` and `import.meta.env.DEV`. - Replace rest `process.env.NODE_ENV` with `import.meta.env.MODE`. - Rename env vars `REACT_APP_*` to `VITE_*`, then replace `process.env.REACT_APP_...` to `import.meta.env.VITE_...`. - Ensure all tests snapshots are actual before upgrading. After upgrading ensure all tests are passing but snapshot-based, then update all snaphots.
|
try checking out https://github.com/bhbs/viject |
|
u can use: npx app_name@latest |
Hi,
I've noticed that the "react-scripts" package hasn't been updated for the past two years. This is causing npm deprecation warnings in my React app for the inner dependencies that react-scripts relies on.
1.Is there any plan to update the react-scripts package in the near future?
2.If not, can you recommend any alternative packages to use instead?
3.Any suggestions on how to address the npm deprecation warnings in the meantime?
I appreciate your support and any insights you can provide on this matter.
npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead npm WARN deprecated @babel/plugin-proposal-async-generator-functions@7.20.7: This proposal has been merged to the ECMAScript standard ality npm WARN deprecated @babel/plugin-proposal-optional-chaining@7.21.0: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated @babel/plugin-proposal-object-rest-spread@7.20.7: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead. npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser npm WARN deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead npm WARN deprecated @babel/plugin-proposal-async-generator-functions@7.20.7: This proposal has been merged to the ECMAScript standard anpm WARN deprecated domexception@2.0.1: Use your platform's native DOMException instead npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin. npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated workbox-cacheable-response@6.6.0: workbox-background-sync@6.6.0 npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1The text was updated successfully, but these errors were encountered: