Closed dillfrescott closed 1 year ago
This failure was introduced when the Lilypad package was added to Hubs Admin. Lilypad v1.7.7 depends on React v18, but it appears to work fine with React v16 in Hubs Admin. A correction to the peer dependencies in Lilypad is forthcoming. In the meantime you can patch bin/init
as follows:
echo -e ${prefix}Initializing Hubs Admin$suffix &&
-mutagen-compose -f "$composefile" run --rm hubs-admin npm install --no-save &&
+mutagen-compose -f "$composefile" run --rm hubs-admin npm install --force --no-save &&
echo -e ${prefix}Initializing Hubs Client$suffix &&
Okay. Thank you
This was fixed with https://github.com/mozilla/hubs/pull/6034 and improved with https://github.com/mozilla/hubs-compose/pull/35. Pull main
and run $ bin/services-update
, then you should be good to $ bin/init
.