FYI: The Blockly Team has created a Github issue for our problem. Like some time ago, this is again caused by the blockly node that creates frequently a new Blockly instance (instead of creating only a new workspace). That seems to be a bit unorthodox use of Blockly, which is why we run from time to time into (breaking) changes. So we will have to wait for a fix...
Since node-red-contrib-blockly works fine using Blockly 10.2.2, would you consider releasing a 2.4.1 with it set to that.
Both my main instance seem to work fine with 10.2.2 so I don't think there is a downside to doing so.
Consider it done:
1 Like
Just tried it on my Pi5 and one running in a VM and seems to work fine 
1 Like
I forgot to mention that the release notes contain 3 small fixes...
3 Likes
Thank you so much @BartButenaers and @cymplecy for the effort you put into this. I can confirm Blockly is working correctly
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
