Magnus Reeves
Magnus Reeves
> I've been following this issue, and I can see that it has been open for a considerable amount of time. I understand that addressing memory leak issues can be...
> using npm-force-resolutions doesn't fundamentally resolve the issue since running npm ls glob may still show that the old, vulnerable version of the glob package is present in your dependency...
Does anyone know which version of node it works on ? Currently have this issue with node 20, running ts-node --esm in a module