Markdown misparses certain links #6944
Assignees
Comments
starpit
added a commit
to starpit/kui
that referenced
this issue
Feb 3, 2021
As described in the issue, the fix requires re-generating our package-lock.json. Unfortunately, doing so also introduces a bug due to a webpack hidden dependence. So we need to bump the webpack and webpack-cli deps, as well. Fixes kubernetes-sigs#6944
starpit
added a commit
that referenced
this issue
Feb 3, 2021
As described in the issue, the fix requires re-generating our package-lock.json. Unfortunately, doing so also introduces a bug due to a webpack hidden dependence. So we need to bump the webpack and webpack-cli deps, as well. Fixes #6944
starpit
added a commit
to starpit/kui
that referenced
this issue
Feb 3, 2021
As described in the issue, the fix requires re-generating our package-lock.json. Unfortunately, doing so also introduces a bug due to a webpack hidden dependence. So we need to bump the webpack and webpack-cli deps, as well. Fixes kubernetes-sigs#6944
starpit
added a commit
to starpit/kui
that referenced
this issue
Feb 3, 2021
As described in the issue, the fix requires re-generating our package-lock.json. Unfortunately, doing so also introduces a bug due to a webpack hidden dependence. So we need to bump the webpack and webpack-cli deps, as well. Fixes kubernetes-sigs#6944
starpit
added a commit
that referenced
this issue
Feb 4, 2021
As described in the issue, the fix requires re-generating our package-lock.json. Unfortunately, doing so also introduces a bug due to a webpack hidden dependence. So we need to bump the webpack and webpack-cli deps, as well. Fixes #6944
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This markdown source is misparsed:
with a strange href.
This bug is fixed by a more recent version of a transitive dependence of
remark-gfm. We will need to re-generate our package-lock.json in order to pick up the fix.Note: doing so will require us to bump our versions of webpack and webpack-cli, because it seems that they, yet again, have the same problem: they have some hidden transitive dependence that they refuse to pin, and so our package-lock.json may express a buggy combination of versions on the webpack side.
ref: remarkjs/remark-gfm#8
The text was updated successfully, but these errors were encountered: