Mudit

@joelarson4 it does in develop branch @fdelbos I have opened a pull request that fixes this bug

@super-kamil https://github.com/zeusdeux/Numeral-js/commit/c620b580d533063354fc31fc05d867e56609c100 There’s a many year old PR with this change but I doubt it’s been merged.

Maybe even get some tests in before doing that?

@karlhorky @agilgur5 Any way us non-yarn users can sort this security alert out without having to add yet another dependency to add resolutions support to npm via a third party...

Gotcha. Thanks @karlhorky! And appreciate the quick response! 🙏🏼

Fair. Do I understand correctly that in this case all `tsdx` users are then stuck with an open vulnerability until tsdx upgrades jest?

Yupp, that's my worry as well. I think it's time to rip this out as a dependency from our projects.

Just did and `marked.parse('[Some link](https://something.xyz/(12)/1)')` returns `'Some link\n'` which looks correct so maybe the update in this package would work! ^_^

I've tried updating this package but it's incredibly hard as all the tests fail as soon as I switch to a newer version of marked. Could you help with that...

We are using this in production as well. But if this sees no activity we are going to be shifting to solutions provided by @squaremo