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
We have the next major release of blockly in beta right now. However, most of the plugins have not yet been updated to be compatible with that version. Anyone who is using any plugins will not be able to cleanly use blockly@beta until they can also use beta versions of the plugins that are listed as compatible with the beta. The issue is the peerDependencies for each plugin specify a version of Blockly that does not include the beta, so npm install will fail as the peer dependencies are not met. See https://groups.google.com/g/blockly/c/MpMkF-hgloA for more context.
The following bugs need to be resolved before this is possible:
Note that the following plugins have already been released as beta versions. If a project depends only on plugins listed below, then these dependencies are already compatible with blockly@beta.
block-test
eslint-config
dev-scripts
dev-tools
theme-dark
theme-deuteranopia
theme-highcontrast
theme-tritanopia
(If you are wondering how this list was derived, it is all of the plugins that dev-tools rely on that also rely on blockly, plus the plugins related to eslint)
The text was updated successfully, but these errors were encountered:
Note that for the plugins that have already been released as beta, that was done by hand and not with Lerna. If we run into lerna having version issues next time we use it, it's almost certainly because of this, but I don't think there was a way around it since not all of the packages were ready to publish.
tbh I'm not sure whether we want to commit these to the repo or let lerna do it when we're ready to release all of them, so I'm just leaving this here so I can decide later.
We have the next major release of blockly in beta right now. However, most of the plugins have not yet been updated to be compatible with that version. Anyone who is using any plugins will not be able to cleanly use blockly@beta until they can also use beta versions of the plugins that are listed as compatible with the beta. The issue is the
peerDependencies
for each plugin specify a version of Blockly that does not include the beta, sonpm install
will fail as the peer dependencies are not met. See https://groups.google.com/g/blockly/c/MpMkF-hgloA for more context.The following bugs need to be resolved before this is possible:
Note that the following plugins have already been released as beta versions. If a project depends only on plugins listed below, then these dependencies are already compatible with blockly@beta.
(If you are wondering how this list was derived, it is all of the plugins that
dev-tools
rely on that also rely on blockly, plus the plugins related to eslint)The text was updated successfully, but these errors were encountered: