NodeJS console not responding to input commands?

After npm start and run a case study I am unable to enter anything in the just Have to close it,but when I start a new statr using npm error npm ERR! code ENOENT

npm ERR! syscall open

npm ERR! path C:\Users\???????\package.json

npm ERR! errno -4058

npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\???????\packag e.json'

npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent

npm ERR! A complete log of this run can be found in:

npm ERR! C:\Users\???????\AppData\Roaming\npm-cache_logs\2019-12-12T18_36_3 1_735Z-debug.log

Saves only the removal of my app,saving copies of files index.js and index.css and the subsequent re-creating the root folder of my app.. How to solve the problem?And how to use the command npm stop? To register in pacag.json?
April 3rd 20 at 17:43
2 answers
April 3rd 20 at 17:45
1. It is very doubtful that the root folder of the project coincided with a folder of the user on the computer.
We must first go to the folder with the project, and then to run there team.

2. If at start there is a watch to stop this process, logically, should remain hanging constantly. He needs to track files. To stop this case, you can press ctrl+c and agreeing with the proposal.

If you need to run any more commands, just open a second instance of the console without stopping start

p.s. well and still there are problems with Russian letters and/or spaces in paths
Yes indeed,moved into the project folder and all start, and thanks about the Ctrl+c - Lorenza.Kuvalis commented on April 3rd 20 at 17:48
April 3rd 20 at 17:47
What's wrong with the error? There are written ENOENT (hereinafter rough translation) there is no input file. Ie entry-point/start. See what you have in the package.json is written in the main? Well and generally check you are doing everything (for tutorials)
"name": "my-app",
"version": "0.1.0",
"private": true,
"dependencies": {
"@testing-library/jest-dom": "^4.2.4",
"@testing-library/react": "^9.3.3",
"@testing-library/user-event": "^7.1.2",
"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-scripts": "3.3.0"
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-test scripts",
"eject": "react-scripts eject"
"eslintConfig": {
"extends": "react-app"
"browserslist": {
"production": [
"not dead",
"not all op_mini"
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
} - Lorenza.Kuvalis commented on April 3rd 20 at 17:50
it is at the moment,after I re-recreate my-app - Lorenza.Kuvalis commented on April 3rd 20 at 17:53
@Lorenza.Kuvalis, you do not have a main key, add it, putting in the value the relative path to the js file/ts, which is the starting point - amber99 commented on April 3rd 20 at 17:56

Find more questions by tags JavaScriptNode.jsnpm