Alokai•8mo ago

why do i get this ENOENT error during install?

I am following the instructions from here. https://docs.vuestorefront.io/magento/installation-setup/installation.html#installation-using-cli

Installation | Vue Storefront 2 for Magento

Documentation for the Magento connector for Vue Storefront 2

5 Replies

skirianov•8mo ago

something went wrong with the installation, you should be getting logs in the same directory - CLI logs or similar, can you send it here?

unusual_username•8mo ago

from cli_logs.txt: "v16.16.0 🙌 Node.js version is compatible 🐳 Docker is installed and running. v16.16.0 🙌 Node.js version is compatible 🐳 Docker is installed and running." jonodesktop:commerce_apps$ npx @vue-storefront/cli help Vue Storefront's CLI. VERSION @vue-storefront/cli/4.4.0 linux-x64 node-v16.16.0

lucifer_is_back_•5mo ago

my case it was yarn

Error: spawn yarn ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn yarn',
  path: 'yarn',
  spawnargs: []

Error: spawn yarn ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
    at onErrorNT (node:internal/child_process:485:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn yarn',
  path: 'yarn',
  spawnargs: []

I solved it by running the command manually I ran

yarn

yarn

and then

yarn dev

yarn dev

in your case you would need to check the command that is failing by checking docker logs and manually type that command by docker exec -it bash _yourdockercontainername_

@hulahoops I still have many errors, but it runs 🙂

yeetski•5mo ago

@hulahoops make sure you can run docker without sudo

alice•5mo ago

Hi @hulahoops Have you solved this problem yet? Can you share it?

Gaming

Programming

why do i get this ENOENT error during install?