Question

I followed all the steps but the npm run dev run in 3000 and ssr is not working

Posted June 7, 2021 80 views
React

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

Hi there,

Can you share here the exact error that you are getting?

Regrds,
Bobby

  • E:\vodafone\myplexspalite>npm run dev

    my-app@0.1.0 dev E:\vodafone\myplexspalite
    npm-run-all –parallel build dev:*

    my-app@0.1.0 dev:build-server E:\vodafone\myplexspalite
    SET NODE_ENV=development webpack –config webpack.server.js –mode=development -w

    my-app@0.1.0 dev:start E:\vodafone\myplexspalite
    nodemon ./server-build/index.js

    my-app@0.1.0 build E:\vodafone\myplexspalite
    node ./update-build.js && react-scripts build

    Latest build date and time updated in meta.json file

    There might be a problem with the project dependency tree.
    It is likely not a bug in Create React App, but something you need to fix locally.

    The react-scripts package provided by Create React App requires a dependency:

    “babel-loader”: “8.0.5”

    Don’t try to install it manually: your package manager does it automatically.
    However, a different version of babel-loader was detected higher up in the tree:

    E:\vodafone\myplexspalite\node_modules\babel-loader (version: 8.1.0)

    Manually installing incompatible versions is known to cause hard-to-debug issues.

    If you would prefer to ignore this check, add SKIPPREFLIGHTCHECK=true to an .env file in your project.
    That will permanently disable this message but you might encounter other issues.

    To fix the dependency tree, try following the steps below in the exact order:

    1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
    2. Delete node_modules in your project folder.
    3. Remove “babel-loader” from dependencies and/or devDependencies in the package.json file in your project folder.
    4. Run npm install or yarn, depending on the package manager you use.

    In most cases, this should be enough to fix the problem.
    If this has not helped, there are a few other things you can try:

    1. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
      This may help because npm has known issues with package hoisting which may get resolved in future versions.

    2. Check if E:\vodafone\myplexspalite\node_modules\babel-loader is outside your project directory.
      For example, you might have accidentally installed something in your home folder.

    3. Try running npm ls babel-loader in your project folder.
      This will tell you which other package (apart from the expected react-scripts) installed babel-loader.

    If nothing else helps, add SKIPPREFLIGHTCHECK=true to an .env file in your project.
    That would permanently disable this preflight check in case you want to proceed anyway.

    P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!

    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! my-app@0.1.0 build: node ./update-build.js && react-scripts build
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the my-app@0.1.0 build script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    [nodemon] 2.0.4
    [nodemon] to restart at any time, enter rs
    [nodemon] watching path(s): .
    [nodemon] watching extensions: js,mjs,json
    [nodemon] starting react-scripts start ./server-build/index.js

    npm ERR! A complete log of this run can be found in:
    npm ERR! C:\Users\balaj\AppData\Roaming\npm-cache_logs\2021-06-07T182721_733Z-debug.log
    ERROR: “build” exited with 1.
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! my-app@0.1.0 dev: npm-run-all --parallel build dev:*
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the my-app@0.1.0 dev script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

    npm ERR! A complete log of this run can be found in:
    npm ERR! C:\Users\balaj\AppData\Roaming\npm-cache_logs\2021-06-07T182722_382Z-debug.log