Update @lezer/markdown dependency to latest version #6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "update-lezer-markdown-dependency"
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?
Hi!
After upgrading
@codemirror/lang-markdownto the latest version, I had an issue where new list items weren't automatically inserted when pressingEnterwith the cursor at the end of an item in a list.I was able to fix it by upgrading the
@lezer/markdownpackage to the latest version. It took a little while figuring out what the problem was since I hadn't installed the@lezer/markdownexplicitly. Here's a PR that bumps the required version of@lezer/markdown.Best,
Jonatan
The current version range, due to the
^caret, already matches that version. I am not going to re-release every depending package every time I bump a version. Clear your package lock instead, that should get you the current version.Ok 👍!
I was unsure if you'd want to merge this or not, but thought it's easy to close the PR if not :), and that it might make sense to set a higher minimum version if the latest version is incompatible with
1.0.0.Clearing package-lock in a big project might cause a lot of unrelated packages to upgrade which might be undesired.
The alternative, leaving transitive dependencies on some random old version forever, isn't great either though.
@heyman I had the same issue with
@lezer/markdown. Runningnpm update @lezer/markdownshould help update the package in the lock file without explicitly installing it inpackage.jsonfile.Pull request closed