You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While setting up a dev environment, vagrant up should work as expected and the service should come up.
Current Behavior
Running:
TBA_LOCAL_DOCKERFILE=true vagrant up
Encountering the following error:
[...]
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.
Presumably because the node modules could not be installed, the service cannot start -- observing this when running ./ops/dev/host.sh:
==> 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
Possible Solution
Bump material-ui dependency to updated version (package seems to be deprecated in favor of @material-ui/core or bumped to v5+)
It does seem like after pulling in the changes from #5963 my dev env is functional.
IMO (as someone with no familiarity or real stake in the project) #5906 seems like a valuable initiative to get things overall more up to date (e.g. material-ui -> @material-ui/core v4 -> @mui/material v5). However, that seems like a more involved effort, and the issue of being unable to spin up an environment to get unblocked seems fixed.
Expected Behavior
While setting up a dev environment,
vagrant up
should work as expected and the service should come up.Current Behavior
Running:
Encountering the following error:
Presumably because the node modules could not be installed, the service cannot start -- observing this when running
./ops/dev/host.sh
:Possible Solution
Bump material-ui dependency to updated version (package seems to be deprecated in favor of
@material-ui/core
or bumped to v5+)Steps to Reproduce (for bugs)
TBA_LOCAL_DOCKERFILE=true vagrant up
Context
Can't successfully start a local dev environment.
Your Environment
The text was updated successfully, but these errors were encountered: