I'm building vscode using the instructions here https://github.com/Microsoft/vscode/wiki/How-to-Contribute#build-and-run-from-source. When I get to the yarn run watch command, it hangs at Finished compilation with 0 errors after 54926 ms. What's going on?
nodejs: 8.9.4
yarn 1.3.2
npm 5.6.0
I was running yarn run watch and encountered this problem. I checked with du -s in the repo's folder a few times: no change, so I killed the command.
After killing yarn run watch I then ran yarn watch and once again it hung with the same error. I checked with du again. No change. I killed that command too.
I then ran
./scripts/code.sh
And VS Code started fine. So in my experience, it is fine to kill the yarn command.
Related
whenever I run yarn start/ yarn install / or any sort of method relating yarn won't work.
however, npm does work. How do I fix this problem?
I've tried to downgrade the node.js version
but it won't work.
I think it's a permission issue. Try adding the "sudo" prefix to the command
I have installed nodemon using yarn but somehow it is showing command not found. I have been trying to get solution but not getting any yet. whenever I use nodemon command it shows nodemon: command not found
I have tried installing yarn global add nodemon and also yarn add nodemon. I had even tried installing dev dependencies.
Whenever I try installing using npmit works but not for yarn.
Can anyone help me out of it how can I solve this using yarn?
Use yarn nodemon command in terminal, it will work for yarn install.
example:
yarn nodemon index
I have an issue with my Nest js API.
When I build in local, all works fine and I can build and start the development server without problems, but when I go to my server I can't build or start the development server.
When I try to run "npm run build","yarn build" or start the server with "yarn start" the node returns to me this error:
I tried to run "export NODE_OPTIONS=--max_old_space_size=4096" and in the ~/.bashrc export de node options with more space. Also, i upgraded all dependencies, and deleted and installed again, but nothing works. I have the same issue with the frontend of this project that uses Next JS.
The server is an aws EC2 t3.small server with Ubuntu 20.04.3 LTS, the node version is v17.3.0, the npm version is 8.3.0 and the yarn version is 1.22.17.
When I run "tsc --extendedDiagnostics --noEmit" i have 20 errors from node_modules/#nestjs/config, I tried to update the package but doesn't work:
And finally, I get this summary:
Thanks
Well, after few hours searching a solution I updated the nest project with the command "sudo nest update --force", I removed the node_modules and executed "yarn install".
After this, I granted all the permissions to my project files with "sudo chmod -R 777 ./" and finally the "npm run build" and "yarn build" worked.
Thanks a lot!
I have started with react.js recently. I am currently using node -v : v12.18.1 and In order to make a react app I am using:
npx create-react-app my-app
But on running this command something unexpected happens. My command prompt gets paused indefinitely as soon as things related to npm audit are shown on the screen
Click here to see the output
I have tried waiting for an hour but nothing happened. As a result, I have to force stop the process by using Ctrl+C
I have tried the following things:
1: clearing cache using npm cache clean --force and verifying it using npm cache verify
2: I have even tried re-installing node.js and uninstalling create-react-app using npm uninstall -g create-react-app and then installing it again.
3:I have even tried using yarn and npm but a similar error was shown in them too.
Try the following command:
npm install npm#latest -g
Then close terminal.
Open a new terminal window and try npx create-react-app my_app
This problem arises due to the stalling of the command prompt. As mentioned in the question the terminal hangs and only node_modules folder is created and at the end most of the users end up terminating the process.
In order to solve this problem I opened the task manager and found a leaf symbol infront of my command propmt. However having this symbol is not a necessary condition.
Img: Showing a suspended process
Later I found that the process was suspended by the system due to some reasons.
I traced it down in the Resource monitor and resumed it.
Img:Resuming a process
Happy Hacking !!!
I'd really like to get yarn working with TeamCity or Jenkins, however
yarn install consumes all my build server's cpu & memory, even with
a tiny npm project. Any idea why?
Summary
yarn install, when run by TeamCity or Jenkins, consumes most CPU/memory, never finishes
running yarn install from the command line on the build server works (finishes in a few seconds)
npm install completes in a few seconds when run by TeamCity/Jenkins
build server: Windows Server 2012, 2 cores, 4GB mem
yarn version 1.6.0
Jenkins version 2.107.2
TeamCity version 2017.2.3
Have tried Node.js versions 8.11.1 and 9.11.1
Details
Steps:
Create a tiny npm project:
mkdir temp
cd temp
yarn init # all defaults
yarn add dummy-module # tiny test package
Commit this to git, set up a Jenkins or TeamCity build with a single command yarn install.
The build never finishes, with the last line of console output: yarn install v1.6.0.
At this time, the Node.js process is consuming most of the CPU and memory on the
build machine. Changing the command to npm install makes it run successfully.
Since it's common to Jenkins and TeamCity, it seems like the problem is to do with
running sub processes from java. I can't find any indication of what's going wrong
in either the TeamCity or Jenkins logs. When aborting the Jenkins build,
I see the following in jenkins.err.log:
Apr 22, 2018 8:59:11 AM hudson.model.Run execute
INFO: master-cake #9 aborted
java.lang.InterruptedException
at java.lang.ProcessImpl.waitFor(Unknown Source)
at hudson.Proc$LocalProc.join(Proc.java:324)
at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
at hudson.model.Build$BuildExecution.build(Build.java:206)
at hudson.model.Build$BuildExecution.doRun(Build.java:163)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
at hudson.model.Run.execute(Run.java:1727)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
I left some crucial information out of the original question - I'm also using yarn's offline mirror, which was stored on a network drive. It turns out that the TeamCity windows service can't access network drives: https://confluence.jetbrains.com/display/TCD10/Known+Issues#KnownIssues-AgentrunningasWindowsServiceLimitations
Relocating yarn's offline mirror to a local directory solved the issue for both TeamCity and Jenkins.