Hi Alfredo, I've updated the vagrant box as per your instructions, but am running into a problem at step 5, "vagrant up". After a lot of success, a call to 'npm prune' exits with an error. Any ideas?
Here is part of the log, where things go wong: ... VERBOSE: Execute-Command Started (C:\installer\staging\windows : npm prune --production). unbuild [email protected] ... unbuild [email protected] VERBOSE: 'npm' exited with 1 Stderr from the command: Cloning into 'C:\installer'... Note: checking out '969b8cd247fe1a4bf744689be3dbf416019ab945'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b <new-branch-name> npm ERR! Windows_NT 10.0.15063 npm ERR! argv "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "prune" "--production" npm ERR! node v6.9.1 npm ERR! npm v3.10.8 npm ERR! path C:\installer\staging\windows\node_modules\.bin\cdl npm ERR! code EEXIST npm ERR! Refusing to delete C:\installer\staging\windows\node_modules\.bin\cdl: is outside C:\installer\staging\windows\node_modules\cardinal and not a link npm ERR! File exists: C:\installer\staging\windows\node_modules\.bin\cdl npm ERR! Move it away, and try again. npm ERR! Please include the following file with any support request: npm ERR! C:\installer\staging\windows\npm-debug.log Installation process returned error code: 1 At C:\tmp\Provisioning.psm1:44 char:5 + throw "Installation process returned error code: $($exitCode)" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Installation pr...d error code: 1:String) [], RuntimeException + FullyQualifiedErrorId : Installation process returned error code: 1 On 2017-07-16 3:08 PM, Alfredo Matas wrote: > Hi all, > > I have updated the windows10-eval-x64-Apps Vagrant box which is now > based on the Windows 10 "creators update" and it also mounts the > Vagrant folder as v: drive. > > To use the new box in a existing project: > 1. Save the content of the VM if needed > 2. vagrant destroy -f > 3. vagrant box update > 4. vagrant box prune > 5. vagrant up > > To list the current Vagrant environments: > > vagrant global-status > > The v: drive seems to work fine with the Doit application. For example: > > do.ps1 -c 'dir v:' > > -- > Alfredo > > > _______________________________________________ > Architecture mailing list > [email protected] > http://lists.gpii.net/mailman/listinfo/architecture -- ;;;;joseph. 'Call me hobophobic, but I don't think two vagrants should be allowed to marry.' - J. Tiedrich - _______________________________________________ Architecture mailing list [email protected] http://lists.gpii.net/mailman/listinfo/architecture
