Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C create-react-app
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,547
    • Issues 1,547
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 417
    • Merge requests 417
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Meta
  • create-react-app
  • Issues
  • #7442
Closed
Open
Issue created Jul 28, 2019 by Administrator@rootContributor

from node-10-16 lts, impossible to run nm start after npx create-react-app my_app [closed]

Created by: jerome-diver

Describe the bug

from node-10-16 lts, impossible to run nm start after npx create-react-app my_app errors are: events.js:174 throw er; // Unhandled 'error' event ^

Error: spawn /usr/bin/palemoon ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) Emitted 'error' event at: at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! memory@0.1.0 start: react-scripts start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the memory@0.1.0 start 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! /home/jerome/.npm/_logs/2019-07-28T06_52_10_841Z-debug.log

after installed package-lock.json, as suggested above, the server doesn't start and no error message.... yarn.lock installed but node_modules can not with many error again: npm ERR! code ETARGET npm ERR! notarget No matching version found for undefined@node_modules npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: npm ERR! /home/jerome/.npm/_logs/2019-07-28T06_54_34_517Z-debug.log

npm version is 6.10.2

I don't want to remove my official repos packages (it is a very bad practice) ad i hope it is possible to just use react with lts node application,if not, it housld be impossible ofr me to learn and use react due to miss-respect version lts concept and unmaintainable applications from this crucial point.

Environment

npx create-react-app --info

Environment Info:

System: OS: Linux 5.2 Arch Linux CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz Binaries: Node: 10.16.0 - /usr/bin/node Yarn: Not Found npm: 6.10.2 - /usr/bin/npm Browsers: Chrome: Not Found Firefox: 68.0.1 npmPackages: react: ^16.8.6 => 16.8.6 react-dom: ^16.8.6 => 16.8.6 react-scripts: 3.0.1 => 3.0.1 npmGlobalPackages: create-react-app: 3.0.1

Steps to reproduce

  1. npm install -g create-react-app
  2. npx create-react-app my_app
  3. cd my_app
  4. npm start

Expected behavior

server should run with information about server access url

Actual behavior

err_at_react_app_start

Assignee
Assign to
Time tracking