Eelco Lempsink

@schell I’m still watching the repository, but @ggreif is doing excellent work and is way more on top of it (thanks!)

I dug into this and found the underlying bug: https://github.com/dependents/node-filing-cabinet/issues/102

Ignore that, this seems to be another issue. When I (explicitly) pass `madge` the `--ts-config` option that points to a file with `{ "compilerOptions": { "module": "esnext", "moduleResolution": "node" }...

So, it seems the bug can be attributed to different things: - `filing-cabinet` has an odd default, that does not match the TypeScript default - `madge` is not automatically picking...

Hey @jperals, Framer doesn’t have semantic versioning, which makes it not so nice to work with in combination with npm. It’s (therefore?) not a popular use case either, making this...

Apologies, this has been fixed now!

I assume the tests were temporarily broken, so this might work after a rebase? I’m interested in this fix landing 😊

I’m experiencing the same issues in a Deno project based on [Slack’s starter template](https://github.com/slack-samples/deno-starter-template). There are no big files to ignore. I have to restart the language server pretty much...