-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Problems with Yarn symlinks (bin-links) under Windows host with Vagrant Linux guest #229
Comments
I have same issues using Docker Toolbox with Windows 10 on the host machine. |
@Rynaro Could you pull in latest master |
@gauravtiwari . Sure, I will setup the same configuration Windows system with Vagrant (+ Ubuntu) workspace that gives to me this issue behavior. |
This is fixed now on latest master. Please update webpacker, re-run installer to replace binstubs and try again 👍 |
@gauravtiwari I've checked here. And is really fixed, based on master branch! |
Awesome 👍 |
@Rynaro @gauravtiwari Hi, you can share your vagrant file, package.json. I cant made works in windows with vagrant ubuntu. |
@estvmachine Are you getting any errors? Please could you share the problem. |
@gauravtiwari I did a ticket in #562 but basically is the same problem exposed here, from windows i use a vagrant ubuntu machine that always give me the error with symlink associated to '../acorn/bin/accorn' and symlink associated to '../../../multicast-dns/cli.js', this is when i tried to use 'rails webpacker:install' |
@estvmachine Ohh, sorry I missed that one but from the logs this seems to be related to yarn. Can you try reinstalling dev server using npm instead - May be you should file the same issue to yarn repo :) |
hi try to do that but works :(. Is a problem with vagrant, but others people can solved for their problems, but i dont know what to do for webpacker: hashicorp/vagrant#6188 |
I'm not sure if this issue is a problem for anyone else but I was able to work around it by stopping vagrant and just running yarn install in the synced folder and then vagrant up and everything worked fine. One thing to note though since I did this outside of the vm when I do vagrant up it says cannot find base. To fix that find your box id and do |
I think it's Yarn problem, but if we consider all ways to work with Rails, we need to consider a Windows running a Vagrant instance as a development environment. (Is one of my available environments to work. And with this environment, fortunately I get the problem)
Vagrant uses the host filesystem to hold the guest filesystem. And when we call a npm, or yarn action to install or configure, we will get a problem to create symlinks like
.bin
folders. And this behaviour avoids the webpacker:install to create some environment files likemanifest.json
. After some warnings, and link errors, the installations return a success for webpacker installation.I see both Yarn and NPM has the
--no-bin-links
, I think it's a great idea to include a argument on install to create this behavior. Or add other ways to configure the webpacker on Vagrant on Windows.Note: In Linux with a Linux Vagrant the webpacker works well. I only found this "problem" in Windows with Linux Vagrant.
The text was updated successfully, but these errors were encountered: