Reed von Redwitz

Hey @iuioiua, I picked this one up since it seemed to be missing documentation. Opened a new PR.

@marvinhagemeister, I think this can be closed. Looks like two issues were resolved with https://github.com/denoland/fresh/pull/1188, but this one should have been closed as well.

Yes, I think providing an opinionated project structure section is a great idea. Otherwise there will be followup questions asking those things. Overall it looks like you're on the right...

I should also mention that I have this implemented with 100% test coverage. (I'm aware that coverage isn't the end-all be-all, but it's better than having 0% coverage.) Let me...

Is this different than #1555?

This sounds cool, although I haven't had time to look in detail. But after a quick glance at the changes, there are some basics that need taking care of: 1....

Regardless of what the code coverage says, if you're adding a new type and not using it, then in my opinion it's not covered. At minimum from a "usage guide"...

Yes, but what about the tests?

I can easily reproduce this with the `deno_graph` project. When I open up https://github.com/denoland/deno_graph/blob/main/js/test.ts in vs code and click "run" on the first test I get: ``` running 1 test...

The error is reproducible with the following minimal case: ```ts import * as esbuild from "https://deno.land/x/[email protected]/mod.js"; Deno.test("esbuild", async (t) => { await t.step("esbuild snapshot with cwd=Deno.cwd()", async () => {...