Eli
@jfmengels, can you take a look? I think all of the snapshot changes are correct, but I just skimmed 'em. The json was particularly intimidating. EDIT: Also, the TS errors...
@jfmengels, ping. I worked around rtfeldman/node-test-runner#636 and then updated snapshots again. I think all of the remaining test failures are snapshots that broke when you added fixes or contained version...
> I **think** all of the remaining test failures are snapshots that broke when you added fixes or contained version numbers. [emphasis added] Figured out why there were a bunch...
> @lishaduck Thank you for all your work! And I'm so sorry for not tending to your pull requests 😞 I'll try to look at the rest of the PRs...
> probably duplicate of [#3533](https://github.com/denoland/std/issues/3533) ? Probably, assuming it wouldn't send it as a 404? I'd need it to be a 200.
See #85.
~~This PR is an absolute mess, but it works. Cleanup later if I have time, I need to hit the hay~~ I say that and then I whip out `grbi`....
Should be good to merge (SemVer minor), but we probably ought to wait until CI's fixed (https://github.com/jfmengels/node-elm-review/issues/176#issuecomment-2325358713).
We really ought to get these closed. See comments in #257.
> Well, there are a lot of pros and lot of cons. Yep. > ## CONS > * it's a very minor nitpick, people might get annoyed at the warnings...