Creating a new project with npm <= 5.2

instructions.md

If you use npm 5.1 or earlier, you can't use npx. Instead, install create-react-app globally:

npm install -g create-react-app

Now you can run:

create-react-app my-app

Try this one if your npm is 6+
npm init react-app my-app
npm init is available in npm 6+
The problems listed above aren't all that serious. This is taking place as a result of an upgrade to the react version.

Try this code

npm init react-app my-app or npm create-react-app my-app
cd my-app
npm start

Gteat

not working with this command please guide me
npm install -g create-react-app
create-react-app my-app

``

__

Please use this code
npm create-react-app my-app
cd my-app
npm start

For everybody who had or may have a problem with installation, here is one example of a solution https://stackoverflow.com/questions/70358474/error-while-creating-new-react-app-you-are-running-create-react-app-4-0-3-w

It works for me. Thanks😇

thanks

Thank you so much. It was helpful me.

https://gist.github.com/gaearon/4064d3c23a77c74a3614c498a8bb1c5f?permalink_comment_id=4324420#gistcomment-4324420

please help

Hi

The error in the image is related to an issue with Node.js's OpenSSL module, specifically regarding digital envelope routines:unsupported. This often occurs when the version of OpenSSL bundled with Node.js is incompatible with certain modules or cryptographic functions being used by the project.

Here are a few steps to resolve this issue:

1. Upgrade react-scripts: Sometimes, older versions of react-scripts can cause compatibility issues. Try updating react-scripts to the latest version:

npm install react-scripts@latest

2. Downgrade Node.js Version: If you're using Node.js version 20.x, it may not be compatible with some older packages. Try downgrading Node.js to an LTS version (such as 18.x or 16.x):

nvm install 18
nvm use 18

3. Set OpenSSL Legacy Provider: Newer versions of Node.js have stricter defaults for OpenSSL. You can force Node.js to use legacy OpenSSL providers by setting the following environment variable:

export NODE_OPTIONS=--openssl-legacy-provider

Alternatively, you can add it directly to your package.json start script:

"scripts": {
"start": "react-scripts start --openssl-legacy-provider"
}

4. Reinstall Node Modules: After making any of the above changes, it's a good idea to delete the node_modules folder and package-lock.json file and then reinstall the dependencies:

rm -rf node_modules package-lock.json
npm install

Try one or more of these solutions to resolve the issue.

Thanks, got it.

…

On Tue, 22 Oct 2024 at 07:22, Arnold Trevor ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Hi The error in the image is related to an issue with Node.js's OpenSSL module, specifically regarding digital envelope routines:unsupported. This often occurs when the version of OpenSSL bundled with Node.js is incompatible with certain modules or cryptographic functions being used by the project. Here are a few steps to resolve this issue: 1. Upgrade react-scripts: Sometimes, older versions of react-scripts can cause compatibility issues. Try updating react-scripts to the latest version: npm install ***@***.*** 2. Downgrade Node.js Version: If you're using Node.js version 20.x, it may not be compatible with some older packages. Try downgrading Node.js to an LTS version (such as 18.x or 16.x): nvm install 18 nvm use 18 3. Set OpenSSL Legacy Provider: Newer versions of Node.js have stricter defaults for OpenSSL. You can force Node.js to use legacy OpenSSL providers by setting the following environment variable: export NODE_OPTIONS=--openssl-legacy-provider Alternatively, you can add it directly to your package.json start script: "scripts": { "start": "react-scripts start --openssl-legacy-provider" } 4. Reinstall Node Modules: After making any of the above changes, it's a good idea to delete the node_modules folder and package-lock.json file and then reinstall the dependencies: rm -rf node_modules package-lock.json npm install Try one or more of these solutions to resolve the issue. — Reply to this email directly, view it on GitHub <https://gist.github.com/gaearon/4064d3c23a77c74a3614c498a8bb1c5f#gistcomment-5245063> or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDQZKZNW4LJ5QFEISTHXSUTZ4XHJLBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVA4DKMRVHA3DKN5HORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

Hello

…

On Tue, Nov 12, 2024, 4:08 PM Humbulan ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ Hello — Reply to this email directly, view it on GitHub <https://gist.github.com/gaearon/4064d3c23a77c74a3614c498a8bb1c5f#gistcomment-5279162> or unsubscribe <https://github.com/notifications/unsubscribe-auth/BDQZKZOK4SRLBZA4P23LUJT2AH4UJBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVA4DKMRVHA3DKN5HORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .