-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@wordpress/block-editor does not work standalone #23332
Comments
The issue is caused by the fact that the block editor was using unstable API from Reakit that was promoted to stable API. It should get resolved in a few days when WordPress packages with related changes are published to npm. Related comment in Reakit library where I ask whether renamed API can be aliased for backward compatibility: ariakit/ariakit#667 (comment) |
#23236 fixes this, but it doesn't help with older versions. 😕 I'll make a patch on Reakit to fix this asap. Ideally, when using experimental modules from npm packages, we should use the exact version in our package.json (without |
It should be fixed now! |
Sorry for the dumb question, but how can I "npm install @wordpress/block-editor" for this particular fix/branch? |
You only need to install a new version of Reakit. |
Describe the bug
A clear and concise description of what the bug is.
@wordpress/block-editor
does not compile/run outside gutenberg.To reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
A standalone gutenberg editor should be initialized
Screenshots
If applicable, add screenshots to help explain your problem.
Editor version (please complete the following information):
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: