Nick Frasser

Hi @plandem, great catch, this is a bug. It's fixed in the latest `v4.0.0-beta.5` (install with `npm install linkifyjs@beta`)

Hi @ymhr, thanks for reporting. This will be fixed in the next major release of Linkify (v4). It's available now in a beta release: ``` npm install linkifyjs@beta npm install...

Unfortunately this is the only way to do it. Note that you don't have to declare a function for each key, you can just set it to `false` e.g., ```js...

There's no great way of going about this unfortunately. I'd suggest running Linkify after the markdown is rendered, with one of the DOM-compatible interfaces: http://soapbox.github.io/linkifyjs/docs/interfaces.html

Hi @cristiann190 , please use [`linkify-string`](https://linkify.js.org/docs/linkify-string.html) instead of `linkify-html` for this case

Fixes as best as possible in the latest [Linkify v4](https://github.com/Hypercontext/linkifyjs/releases/tag/v4.0.0)

Links that begin with `file:` are now supported in the latest [Linkify v4.0](https://github.com/Hypercontext/linkifyjs/releases/tag/v4.0.0)

Due to the reasons [described here](https://github.com/Hypercontext/linkifyjs/issues/351#issuecomment-937393153) it is not possible to solve this with Linkify's current implementation. Note that both v2 and v3 are affected.

@varunsrin > are you considering fixing this for v4? or is this desired behavior for Linkify going forward? Unfortunately no, it would require a complete rethinking of the internal parsing...

Hi @jryans and @Pike, thank you both looking into this! I released v4.0.0-beta.4 some type improvements that should address this.