Open maribethb opened 1 month ago
There seem to be three ways we could go here:
npm install
of the beta before running npm run test:ghpages
.It's not clear what the best approach is.
Per discussion with @rachel-fenichel: recommend going with option 2, since most typically when running this command we're going to be interested in discovering actual incompatibilities between plugins and Blockly beta, rather than discovering (or carefully avoiding) nominal peerDependency version incompatiblities.
Check for duplicates
Component
blockly-samples infrastructure
Description
We recently changed how we structure the dependencies in samples to use hoisting so we eliminate the "two blockly problem"
However running
npm run test:ghpages:beta
will try to install blockly@beta inside every plugin which is now wrong. That's fine for examples where we're not using hoisting. For samples it needs to install blockly@beta at the root of samples. but there might be problems if the plugins say they require a version of blockly that isn't compatible with the beta.Don't run this command until this is fixed
Reproduction steps
Stack trace
No response
Screenshots
No response