Open GoogleCodeExporter opened 8 years ago
I think this is an unfortunate problem caused by the way node.js vendors
dependencies and the Windows max file length path. Basically, node.js installs
dependencies in very long folder structures which can get too long to be
addressed.
Can you try this?
npm install -g npm@3.7
The new version of npm vendors packages differently, which might help here.
Original comment by dlor...@google.com
on 1 Feb 2016 at 4:48
Thanks for the suggestion!
I had a bad feeling about that file length myself, but I don't really know what
to change to pack in a less complicated structure :-(
The 3.7 version didn't help
-----
So you want to continue (Y/n)? y
Beginning deployment...
Verifying that Managed VMs are enabled and ready.
Provisioning remote build service.
Copying certificates for secure access. You may be prompted to create an SSH
keypair.
Building and pushing image for module [default]
----------------------------------------------------- DOCKER BUILD OUTPUT
------------------------------------------------------
Beginning teardown of remote build environment (this may take a few seconds).
ERROR: gcloud crashed (WindowsError): [Error 3] Systemet finner ikke angitt
bane:
'C:\\Users\\Odd\\Dropbox\\cola\\nodejs-getting-started\\2-structured-data\\node_
modules\\gcloud\\node_modules\\gce-images\\node_modules\\google-auto-auth\\node_
modules\\google-auth-library\\node_modules\\gtoken\\node_modules\\google-p12-pem
\\node_modules\\node-forge\\build-flash.xml'
If you would like to report this issue, please run the following command:
gcloud feedback
Deleted
[https://www.googleapis.com/compute/v1/projects/skilled-fulcrum-120422/zones/us-
central1-f/instances/gae-builder-vm-20160201t180417].
Original comment by OddPaa...@gmail.com
on 1 Feb 2016 at 5:09
The Norwegian text "Systemet finner ikke angitt bane:" translates to "System
cannot find path:"
Original comment by OddPaa...@gmail.com
on 1 Feb 2016 at 5:10
Original issue reported on code.google.com by
OddPaa...@gmail.com
on 29 Jan 2016 at 12:24