@nuxt/content: v1.0.0
@nuxt/content-theme-docs: v0.7.2
nuxt: v2.14.7
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.
@nuxt/content to v1.10.0remark-footnotes to v3.0.0 and it has already been published as a part of @nuxt/[email protected].However, as written in the official repo of remark-footnotes or warned in the console of the demo above, [email protected] requires [email protected]. #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.
Ah, I found [email protected] was published 10 days after [email protected] 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?
So there's no immediate solution or workaround until the remark-parse is updated?
Did someone tried yarn add remark-footnotes@2 ?
Did someone tried
yarn add remark-footnotes@2?
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 and package-lock.json -- and did a full npm install.
Everything seems fine -- so for the moment, at least -- this seems like a work around.
Thanks!
From package.json:
"@nuxt/content": "^1.10.0",
"nuxt": "^2.14.7",
"remark-footnotes": "2.0.0"
@cschweda
Thank you for testing!
By the way, it might work as well to install [email protected], removing node_modules and package-lock.json.
Most helpful comment
Yup -- just tried this.
npm i remark-footnotes@2Footnotes seem to render properly -- and I didn't see the installation warning.
Just to make sure, I deleted
node_modulesandpackage-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: