TBA_LOCAL_DOCKERFILE=true vagrant up

[...]
    default: Now using node v18.20.0 (npm v10.5.0)
    default: Running npm install... this may take a while...
    default: npm ERR! code ERESOLVE
    default: npm ERR! ERESOLVE could not resolve
    default: npm ERR!
    default: npm ERR! While resolving: material-ui@0.20.2
    default: npm ERR! Found: react@18.2.0
    default: npm ERR! node_modules/react
    default: npm ERR!   react@"^18.2.0" from the root project
    default: npm ERR!   peer react@">=16.8.0" from @emotion/react@11.11.1
    default: npm ERR!   node_modules/@emotion/react
    default: npm ERR!     @emotion/react@"^11.8.1" from react-select@5.8.0
    default: npm ERR!     node_modules/react-select
    default: npm ERR!       react-select@"^5.8.0" from the root project
    default: npm ERR!   25 more (@emotion/use-insertion-effect-with-fallbacks, ...)
    default: npm ERR!
    default: npm ERR! Could not resolve dependency:
    default: npm ERR! peer react@"^15.4.0 || ^16.0.0" from material-ui@0.20.2
    default: npm ERR! node_modules/material-ui
    default: npm ERR!   material-ui@"^0.20.2" from the root project
    default: npm ERR!
    default: npm ERR! Conflicting peer dependency: react@16.14.0
    default: npm ERR! node_modules/react
    default: npm ERR!   peer react@"^15.4.0 || ^16.0.0" from material-ui@0.20.2
    default: npm ERR!   node_modules/material-ui
    default: npm ERR!     material-ui@"^0.20.2" from the root project
    default: npm ERR!
    default: npm ERR! Fix the upstream dependency conflict, or retry
    default: npm ERR! this command with --force or --legacy-peer-deps
    default: npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
    default: npm ERR!
    default: npm ERR!
    default: npm ERR! For a full report see:
    default: npm ERR! /root/.npm/_logs/2024-04-01T03_18_08_415Z-eresolve-report.txt
    default:
    default: npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-04-01T03_18_08_415Z-debug-0.log
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.

==> default: Doing an initial rsync...
Now using node v18.20.0 (npm v10.5.0)

> tba-react@0.0.0 dev
> cross-env NODE_ENV=development webpack --watch

sh: 1: cross-env: not found

aus@vice /code/the-blue-alliance ❯  node -v
v18.20.0

❯  neofetch --off
aus@vice.local
OS: macOS 14.3.1 23D60 arm64
Host: MacBookPro18,3
Kernel: 23.3.0
Uptime: 15 days, 6 hours, 15 mins
Packages: 286 (brew)
Shell: zsh 5.9
Resolution: 3024x1964
DE: Aqua
WM: Quartz Compositor
WM Theme: Orange (Dark)
Terminal: iTerm2
Terminal Font: FiraCodeNerdFontCompleteM-Retina 13
CPU: Apple M1 Pro
GPU: Apple M1 Pro
Memory: 6450MiB / 32768MiB
Locale: en_US.UTF-8