Chris Krycho

I’ve started working on wiring up twoslash, and it looks like it should do the trick nicely. It current fails with a *lot* of errors, but I’ve made a bunch...

I think I have thought about adding this back in about seven times. 😂 It makes a lot of sense—so much so that we actually *used* to have it, under...

@gluax I hear you! How does this feel? ```ts import { expect, test } from 'vitest'; // etc. import { unwrap, unwrapErr } from 'true-myth/toolbelt'; import { producesMaybe, producesResult }...

It could also work to add them to a `true-myth/test-support` module, which would even *more* loudly signal that these are really only intended for test code—with nothing *stopping* you from...

That’s actually exactly what I ended up doing; see #870 – I’ll go ahead and merge and release it once there’s been time for a bit of feedback!

Released as part of [v8.1.0](https://github.com/true-myth/true-myth/releases/tag/v8.1.0)!

Excellent! As noted on the PR, please feel free to open a PR adding it to the appendix for translations!

It does indeed reproduce in that mode. https://user-images.githubusercontent.com/2403023/214440004-58915119-8816-4e2b-a2fb-e34a38fb41ee.mp4

My colleague @hmajoros did some further debugging and found a bit more info: > vscode attempts to create a TS project to better analyze the non-TS package you are in,...

This is still an issue in our large monorepo; I believe @hmajoros had made a little more progress on why but not much. Net, it seems like Code is trying...