Skip to content

Update Vagrantfile#3

Open
PavloPoliakov wants to merge 1 commit intorobertkowalski:masterfrom
PavloPoliakov:patch-1
Open

Update Vagrantfile#3
PavloPoliakov wants to merge 1 commit intorobertkowalski:masterfrom
PavloPoliakov:patch-1

Conversation

@PavloPoliakov
Copy link

It would not work, unless the symlinks are allowed.
Yesterday I had issues with this.

It would not work, unless the symlinks are allowed.
Yesterday I had issues with this.
@robertkowalski
Copy link
Owner

Hi,

sorry for the broken box - taking a look now!

@robertkowalski
Copy link
Owner

@PavelPolyakov I was not able to reproduce the issue - when does the error happen?

@PavloPoliakov
Copy link
Author

@robertkowalski
The thing is, that I've also experimented with installing the nvm to the vagrant.
Then I've searched if someone had done the same and experienced any issues, found your repo.

Then I've found how the other people had solved any issues, and I learned that we should allow symlinking. That had helped.

I don't know how to reproduce it exactly. You can just leave it as is, and hopefully if someone would met any issue, he would find our dialog :) If everything is working in your case, it could be that my case was unique.

Regards,

@robertkowalski
Copy link
Owner

Thank you for your fast response.

I guess it is related to shared folders - are you using them in your setup?

npm link creates symlinks - so running npm link inside of a shared folder might produce the error.

@PavloPoliakov
Copy link
Author

Yes, I use a shared folder.
And I did a simple npm install .

Anyhow, even more info - when I've used my Vagrant (it's much alike yours) on Windows - I've learned that it's possible to do npm install --no-bin-link, and install everything without creating the symlinks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants