[theme-docs] remark-footnotes plugin doesn't work since version 0.7
See original GitHub issueVersion
@nuxt/content: v1.0.0 @nuxt/content-theme-docs: v0.7.2 nuxt: v2.14.7
Reproduction Link
https://codesandbox.io/s/busy-jennings-vbogj?file=/content/index.md
This demo doesn’t use theme-docs but just forked the one written in the issue template, because the bug is actually due to @nuxt/content
itself.
Steps to reproduce
- Upgrade
@nuxt/content
tov1.10.0
- Use footnotes in markdown contents
- See the rendered page
What is Expected?
- Footnotes are correctly rendered.
- Or, all the remark-related dependencies should have been updated at once.
What is actually happening?
- Footnotes are not correctly rendered.
- Or, major update of remark plugins was published without the dependency.
Additional context (what I found)
#531 major-updated remark-footnotes
to v3.0.0
and it has already been published as a part of @nuxt/content@1.10.0
.
However, as written in the official repo of remark-footnotes
or warned in the console of the demo above, remark-footnotes@3.0.0
requires remark-parse@9.0.0
. #567 is to update remark-parse
but it has not yet been merged and published.
So, until #567 is published, we can’t use footnotes in markdown contents. I’m not sure there is a workaround, though.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5 (1 by maintainers)
Top Results From Across the Web
remark-footnotes - npm
remark plugin to add support for footnotes. Important! This plugin is affected by the new parser in remark ( micromark , see remarkjs/remark#536...
Read more >History | Jekyll • Simple, blog-aware, static sites
fix: pin rubocop to 1.12 due to error with ruby 2.4 (#8651); Load Jekyll plugins from BUNDLE_GEMFILE location (#8585); fix(security): CVE-2021-28834 (#8680) ...
Read more >History - Jekyll • 简单静态博客网站生成器
Update the Code of Conduct to the latest version (#4402) ... (#2899); Add Big Footnotes for Kramdown plugin to list of third-party plugins...
Read more >Doesn't work any more - WordPress.org
[This thread is closed.] So, it's really hard: Multisite installation, footnotes 2.1.0 – on one site it works, on the other not (not…...
Read more >Better Footnotes, Plugin Synergy & an Electron Update
New plugins like incremental writing, inline variable support, ... while versions defines which version works with which Obsidian version.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yup – just tried this.
npm i remark-footnotes@2
Footnotes seem to render properly – and I didn’t see the installation warning.
Just to make sure, I deleted
node_modules
andpackage-lock.json
– and did a fullnpm install
.Everything seems fine – so for the moment, at least – this seems like a work around.
Thanks!
From
package.json
:Ah, I found
remark-parse@9.0.0
was published 10 days afterremark-footnotes@3.0.0
was published. So, it was be just a timing issue, since there is no way the renovate app know the relationship between them and include them into one PR. The app just creates PRs in a certain interval, doesn’t it?