Saem Ghani

> Simple one: https://github.com/inv2004/youtag Which file was it? nimsuggest is started with a project file, so need to know that as well.

This is no longer valid

This should not be added to reports, it's a legacy subsystem and no more stuff should go in there.

An entirely new approach needs to be determined, this isn't a good first issue. I'm closing it for now.

The original issue seems to be solved and we also have the asdf plugin (https://github.com/nim-works/asdf-nimskull), and having x86 and Apple Silicon support in CI, this can be considered resolved.

`knownIssue` has been fully implemented, along with testing for changes to results in CI, considering this complete.

If I specify the `--backend:js` and `-d:js` parameters everything works fine, tested with: * nimble as a project file (the backend specification in the nimble file did nothing, had to...

A workaround(?) for this would be to have the user specify the params in a `nim.cfg` or `$project.nim.cfg`.

This has been superceded by adding in AST diagnostics.

bors r+