RobertByrnes
commented
2 years ago Updating the issue as I have replicated it:
vagrant@homestead:~/code/laravel-projects/moneyscout$ php artisan blast:launch --install
0/3 [â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘â–‘] Installing npm dependencies...
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm notice
npm notice New patch version of npm available! 8.1.0 -> 8.1.3
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.1.3
npm notice Run npm install -g npm@8.1.3 to update!
npm notice
npm ERR! code EPROTO
npm ERR! syscall symlink
npm ERR! path ../@babel/parser/bin/babel-parser.js
npm ERR! dest /home/vagrant/code/laravel-projects/moneyscout/vendor/area17/blast/node_modules/.bin/parser
npm ERR! errno -71
npm ERR! EPROTO: protocol error, symlink '../@babel/parser/bin/babel-parser.js' -> '/home/vagrant/code/laravel-projects/moneyscout/vendor/area17/blast/node_modules/.bin/parser'
npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2021-11-17T22_01_41_297Z-debug.log
Symfony\Component\Process\Exception\ProcessFailedException
The command "'npm' 'ci' '--production' '--ignore-scripts'" failed.
Exit Code: 185(Unknown error)
Working directory: /home/vagrant/code/laravel-projects/moneyscout/vendor/area17/blast
Output:
================
Error Output:
================
at vendor/symfony/process/Process.php:270
266â–• */
267â–• public function mustRun(callable $callback = null, array $env = []): self
268â–• {
269â–• if (0 !== $this->run($callback, $env)) {
➜ 270▕ throw new ProcessFailedException($this);
271â–• }
272â–•
273â–• return $this;
274â–• }
+16 vendor frames
17 artisan:37
Illuminate\Foundation\Console\Kernel::handle()
I discovered an issue with the command
blast:launch --installwhen ssh'ing into vagrant box/homestead. The same babel parser error that gets thrown sometimes when trying to runnpm run devin the same environment. It seems to be caused by simlinks set up between the repos on the windows host and the directories hosting the site in the vagrant box. When running the command from a terminal on the windows host it works fine (using npm installation on windows), after which runningblast:launch(without --install) works from within the vagrant box. The usual work around is the--no-bin-linksargument with the npm command. Will investigate further...