mirror of
https://github.com/plankanban/planka.git
synced 2026-02-05 00:39:58 +03:00
Markdown plugins cause runtime error if not present or incompatible in Planka #727
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @symonbaikov on GitHub (Jun 6, 2025).
When enabling certain markdown plugins in client/src/configs/markdown-plugins/index.js (for example, plugins from @gravity-ui/markdown-editor/markdown-it/* or @diplodoc/transform/lib/plugins/*), and clicking on the third button:
the application crashes with the following error in the browser console:
Details:
The error occurs if a plugin is missing from node_modules or is incompatible with the current markdown parser version.
The problem is not visible at build time, but causes a runtime crash when rendering markdown (especially in list view).
Disabling all external plugins and leaving only local ones (like link and mention) resolves the issue.
The error is triggered by the markdown parser trying to call methods on undefined plugins.
Steps to reproduce:
Add any non-existent or incompatible plugin import to markdown-plugins/index.js.
Add it to the exported plugins array.
Open any board and switch to list view (or any view that renders markdown).
Observe the runtime error in the browser console.
Expected behavior:
The application should either:
Fail gracefully if a plugin is missing or incompatible (with a clear error message),
Or provide a way to validate plugin existence/compatibility at build time.
@symonbaikov commented on GitHub (Jun 6, 2025):
After step-by-step testing, I found that the problem is caused by the
noteplugin (@diplodoc/transform/lib/plugins/notes).When this plugin is enabled in client/src/configs/markdown-plugins/index.js, the application crashes with the following error:
Disabling the note plugin resolves the issue and the markdown rendering works correctly.
It seems that either the plugin is not compatible with the current markdown parser version, or it is missing or broken in the current environment.
@meltyshev commented on GitHub (Jun 6, 2025):
Thanks for reporting! Fixed.