-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NPM issue #1981
Comments
@Kukindoo has this been resolved? or have you tried reinstalling homestead? |
you need to run npm outside of vagrant so in your command prompt goto the laravel folder then you can run |
Yes. I have installed/reinstalled homestead on various machines, and my co-workers attempted this as well, with the same result. We used homestead as all-in-one solution, as some of the machines do not have |
There is a problem with default syncing shared folders. For example, it works:
But it's not a solution for default virtualbox workflow... UPDATE. Fixed for: |
@Kukindoo you need to add a BUT I do suggest that you run |
When I run vagrant
Versions
Host operating system
Windows 10
Homestead.yaml
Expected behavior
npm installing the packages
Actual behavior
vagrant@homestead:~/code/pmmrc$ npm run build
npm ERR! code ENOTSUP
npm ERR! syscall read
npm ERR! errno -95
npm ERR! Could not read package.json: Error: ENOTSUP: operation not supported on socket, read
vagrant@homestead:~/code/pmmrc$ sudo npm install
npm ERR! code ERR_INVALID_ARG_TYPE
npm ERR! The "path" argument must be of type string or an instance of Buffer or URL. Received null
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-06-13T00_23_22_908Z-debug-0.log
Steps to reproduce
The text was updated successfully, but these errors were encountered: