(please read to end to understand my problem)
I am yet not sure how this behavior is related to npm or yarn / node but here what happened to me a few times:
At our work we have a vm using vagrant and virtualbox - it is a custom box - which we are using as a local test environment.
uname -a says
Linux rm-dev 3.2.0-4-amd64 #1 SMP Debian 3.2.73-2+deb7u2 x86_64 GNU/Linux if thats helps.
To my problem:
I installed node.js on the vm using the following commands:
#!/bin/bash # Create and change directory mkdir nodejs cd nodejs # Download archive wget https://nodejs.org/dist/v8.1.4/node-v8.1.4-linux-x64.tar.xz # Extract archive tar -xvf node-v8.1.4-linux-x64.tar.xz # Delete archive rm node-v8.1.4-linux-x64.tar.xz # Copy files to required directories sudo cp -R node-v8.1.4-linux-x64/bin/* /usr/bin/ sudo cp -R node-v8.1.4-linux-x64/include/* /usr/include/ sudo cp -R node-v8.1.4-linux-x64/lib/* /usr/lib/ sudo cp -R node-v8.1.4-linux-x64/share/* /usr/share/ # Go back and delete directory cd .. rm -rf nodejs
After this process I have - obviously - the npm and node binaries available. Everything is fine. Then I have installed
forever - still everything was fine and forever worked without any problems.
But here it comes: When I rebooted the VM the forever binary file
/usr/bin/forever was simply empty. No content anymore. To solve this problem was to uninstall the package, clear npm cache and reinstall it and reboot - until it was not empty anymore.
Since today I could not understand what happens here or why.
Do anyone had this experience yet or have any idea?
Im thankful for every suggestion. If I missed some information which can help to help me - please tell me.