Development Setup Using Vagrant

[hfjlb]

I tried to install using Vagrant, but I am getting errors.

default: Processing triggers for libc-bin (2.27-3ubuntu1) ...
default: ++ npm install -g yarn
default: /tmp/vagrant-shell: line 13: npm: command not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I fixed the problem by modify vagrantfile and make install suecessed.
but I still get error that bixed in in 810e96b

Webpacker can't find application.js in /vagrant/public/packs/manifest.json. Possible causes:

1. You want to set webpacker.yml value of compile to true for your environment
   unless you are using the webpack -w or the webpack-dev-server.
2. webpack has not yet re-run to reflect updates.
3. You have misconfigured Webpacker's config/webpacker.yml file.
4. Your webpack configuration is not creating a manifest.
   Your manifest contains:
   {
   }

---

[hfjlb]

I tried vagrant reload --provision and get next error

default: + yarn
default: yarn install v1.16.0
default: [1/4] Resolving packages...
default: [2/4] Fetching packages...
default: info fsevents@1.2.7: The platform "linux" is incompatible with this module.
default: info "fsevents@1.2.7" is an optional dependency and failed compatibility check. Excluding it from installation.
default: [3/4] Linking dependencies...
default: warning "@rails/webpacker > postcss-cssnext@3.1.0" has unmet peer dependency "caniuse-lite@^1.0.30000697".
default: warning " > webpack-dev-server@3.2.1" has unmet peer dependency "webpack@^4.0.0".
default: warning "webpack-dev-server > webpack-dev-middleware@3.6.0" has unmet peer dependency "webpack@^4.0.0".
default: error An unexpected error occurred: "EPROTO: protocol error, symlink '../../../../js-yaml/bin/js-yaml.js' -> '/vagrant/node_modules/@rails/webpacker/node_modules/.bin/js-yaml'".
default: info If you think this is a bug, please open a bug report with the information provided in "/vagrant/yarn-error.log".

[hfjlb]

I solved the problem buy two steps
1, execute the follow ps command as administrator
fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1
2, modify the vagrantfile
vb.customize ["setextradata", :id, "VBoxInternal2/SharedFoldersEnableSymlinksCreate/vagrant","1"]