2023-06-09 12:18:10 +00:00
|
|
|
{
|
Replace isolated-block-editor in favor of @wordpress/block-editor
Despite the fact that Gutenberg developers did not care at all about
uses of this library outside WordPress until last year[0], and that it
is almost impossible to do something that goes beyond the very basic
without using “private APIs”, they insist that the isolated block
editor should be “deprecated”[1].
I do not particularly care much about the isolated block editor, as it
_does_ use all these private APIs and, thus, it is very difficult to
use unless you use the exact same dependencies, otherwise it emits a
weird error regarding “unlocking” things that are not “locked” (i.e.,
the new-fangled way of “protecting” private APIs[2]). And,
apparently, things got easier with Gutenberg 18.5 with the
introduction of the BlockCanvas.
However, it is still a very frustrating experience, and the
documentation for most components and packages is next to
non-existent.
Nevertheless, i managed to get a barely functional editor that still
has some missing features, like the color of rich texts’ highlight
format[3], but it i believe it is a good base to grow the custom
editor on top of.
[0]: https://github.com/WordPress/gutenberg/issues/53874
[1]: https://github.com/WordPress/gutenberg/issues/57672#issuecomment-1883119040
[2]: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-private-apis/
[3]: https://github.com/WordPress/gutenberg/issues/55036
2024-06-14 01:24:07 +00:00
|
|
|
"name": "tipus",
|
|
|
|
"version": "0.0.0",
|
|
|
|
"type": "module",
|
|
|
|
"description": "Single page editor",
|
|
|
|
"author": "Tàndem",
|
|
|
|
"license": "AGPL-3.0-or-later",
|
|
|
|
"scripts": {
|
|
|
|
"dev": "vite",
|
|
|
|
"build": "vite build",
|
|
|
|
"preview": "vite preview"
|
|
|
|
},
|
|
|
|
"dependencies": {
|
|
|
|
"@wordpress/block-editor": "13.0.0",
|
|
|
|
"@wordpress/block-library": "9.0.0",
|
|
|
|
"@wordpress/components": "28.0.0",
|
2024-06-14 17:40:49 +00:00
|
|
|
"@wordpress/data": "^10.0.0",
|
Replace isolated-block-editor in favor of @wordpress/block-editor
Despite the fact that Gutenberg developers did not care at all about
uses of this library outside WordPress until last year[0], and that it
is almost impossible to do something that goes beyond the very basic
without using “private APIs”, they insist that the isolated block
editor should be “deprecated”[1].
I do not particularly care much about the isolated block editor, as it
_does_ use all these private APIs and, thus, it is very difficult to
use unless you use the exact same dependencies, otherwise it emits a
weird error regarding “unlocking” things that are not “locked” (i.e.,
the new-fangled way of “protecting” private APIs[2]). And,
apparently, things got easier with Gutenberg 18.5 with the
introduction of the BlockCanvas.
However, it is still a very frustrating experience, and the
documentation for most components and packages is next to
non-existent.
Nevertheless, i managed to get a barely functional editor that still
has some missing features, like the color of rich texts’ highlight
format[3], but it i believe it is a good base to grow the custom
editor on top of.
[0]: https://github.com/WordPress/gutenberg/issues/53874
[1]: https://github.com/WordPress/gutenberg/issues/57672#issuecomment-1883119040
[2]: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-private-apis/
[3]: https://github.com/WordPress/gutenberg/issues/55036
2024-06-14 01:24:07 +00:00
|
|
|
"@wordpress/element": "6.0.0",
|
2024-06-14 16:04:59 +00:00
|
|
|
"@wordpress/format-library": "5.0.0",
|
2024-06-15 01:34:15 +00:00
|
|
|
"@wordpress/icons": "10.0.0",
|
2024-06-14 16:04:59 +00:00
|
|
|
"@wordpress/interface": "6.0.0"
|
Replace isolated-block-editor in favor of @wordpress/block-editor
Despite the fact that Gutenberg developers did not care at all about
uses of this library outside WordPress until last year[0], and that it
is almost impossible to do something that goes beyond the very basic
without using “private APIs”, they insist that the isolated block
editor should be “deprecated”[1].
I do not particularly care much about the isolated block editor, as it
_does_ use all these private APIs and, thus, it is very difficult to
use unless you use the exact same dependencies, otherwise it emits a
weird error regarding “unlocking” things that are not “locked” (i.e.,
the new-fangled way of “protecting” private APIs[2]). And,
apparently, things got easier with Gutenberg 18.5 with the
introduction of the BlockCanvas.
However, it is still a very frustrating experience, and the
documentation for most components and packages is next to
non-existent.
Nevertheless, i managed to get a barely functional editor that still
has some missing features, like the color of rich texts’ highlight
format[3], but it i believe it is a good base to grow the custom
editor on top of.
[0]: https://github.com/WordPress/gutenberg/issues/53874
[1]: https://github.com/WordPress/gutenberg/issues/57672#issuecomment-1883119040
[2]: https://developer.wordpress.org/block-editor/reference-guides/packages/packages-private-apis/
[3]: https://github.com/WordPress/gutenberg/issues/55036
2024-06-14 01:24:07 +00:00
|
|
|
},
|
|
|
|
"devDependencies": {
|
|
|
|
"@vitejs/plugin-react": "^4.3.1",
|
|
|
|
"sass": "^1.77.0",
|
|
|
|
"vite": "^5.2.0"
|
|
|
|
}
|
2023-06-09 12:18:10 +00:00
|
|
|
}
|