chore: upgrade remarkable dependency#199
Open
mnahkies wants to merge 2 commits intojonschlinkert:masterfrom
Open
chore: upgrade remarkable dependency#199mnahkies wants to merge 2 commits intojonschlinkert:masterfrom
mnahkies wants to merge 2 commits intojonschlinkert:masterfrom
Conversation
mnahkies
commented
May 17, 2025
Author
There was a problem hiding this comment.
I'd be tempted to replace this with a github actions workflow
mnahkies
commented
May 17, 2025
| require('minimist'); | ||
| require('mixin-deep', 'merge'); | ||
| require('object.pick', 'pick'); | ||
| require('remarkable', 'Remarkable'); |
Author
There was a problem hiding this comment.
When continuing to use lazy-cache I got a Remarkable is not a constructor error. I'm not sure that there is much value in lazy-cache for remarkable when it's doing the majority of the heavy lifting for this module.
mnahkies
added a commit
to mnahkies/ng-qrcode
that referenced
this pull request
Oct 26, 2025
`markdown-toc` appears somewhat abandoned, with a PR I raised to upgrade `remarkable` going unlooked at ~6 months. (ref: jonschlinkert/markdown-toc#199) replace it with `remark` / `remark-toc` to clear CVE warnings.
mnahkies
added a commit
to mnahkies/ng-qrcode
that referenced
this pull request
Oct 26, 2025
`markdown-toc` appears somewhat abandoned, with a PR I raised to upgrade `remarkable` going unlooked at ~6 months. (ref: jonschlinkert/markdown-toc#199) replace it with `remark` / `remark-toc` to clear CVE warnings.
mnahkies
added a commit
to mnahkies/openapi-code-generator
that referenced
this pull request
Oct 26, 2025
`markdown-toc` appears somewhat abandoned, with a PR I raised to upgrade `remarkable` going unlooked at ~6 months. (ref: jonschlinkert/markdown-toc#199) replace it with `remark` / `remark-toc` to clear CVE warnings.
mnahkies
added a commit
to mnahkies/openapi-code-generator
that referenced
this pull request
Oct 26, 2025
`markdown-toc` appears somewhat abandoned, with a PR I raised to upgrade `remarkable` going unlooked at ~6 months. (ref: jonschlinkert/markdown-toc#199) replace it with `remark` / `remark-toc` to clear CVE warnings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
remarkableto the latest version, which removes some problematic dependencies causing CVE's to be flagged by automated scanners