GitMurf

Yeah I agree. I tested with simple non dynamic names and still getting errors. Are you all on windows? I wonder if it's a path / escaping issue like most...

@AlansCodeLog @kirylvarykau do you also happen to be using Windows?

> I've found another edge case, apparently, template strings alone (no variables) can't be used either. I was working on a parser and I did not want to escape the...

@Daydreamer-riri are you on Windows?

> Not sure if this is not worth the effort because work on the proper solution is almost done. @weilbith can you point me to where this work is currently...

fyi @marilari88 @lucax88x Vitest finally landed (v2.0) the `vitest list` cli api that was mentioned above. See here: https://github.com/vitest-dev/vitest/releases/tag/v2.0.0 Here are the docs for vitest list: https://vitest.dev/guide/cli#vitest-list This is how...

Btw for anyone that is still trying to tackle this PR (I cannot as do not have time right now and am too uneducated on the neotest adapter "internals" etc.)...

@Daydreamer-riri since this is a different issue (related to running template ".each()" tests) lets discuss in the other Issue... I just responded to you there.

Any updates or advice from the team on this? I am also getting the same Type error of `...keys, entries, toJSON, isValid, and 8 more...` and am wondering what the...

It still seems like this plugin is one of the most popular but it seems as if it has not been touched since it was released a few years ago....