Reed von Redwitz

Are we sure this is working? In a clean project I tried to do the following: ``` deno vendor main.ts deno run -A --no-remote main.ts ``` and got the following:...

Thanks @secext2022 , that sorted out the `remote specifier` error. I will create some documentation about vendoring a Fresh project using this information. @marvinhagemeister, what do you think about closing...

This should also be closed now that we have documentation for using `deno_kv_oauth` as well: https://fresh.deno.dev/docs/examples/using-deno-kv-oauth.

Sorry, I should have mentioned that. Of course I was deleting the coverage dir prior to running the tests. (Exactly for that reason -- to ensure nothing was left behind.)...

I'll spare all the details of how I got to this point, but I ended up changing my test to be the following: ```ts import { assert, assertEquals } from...

@hashrock, I think this can be closed. When I go to https://deno.land/x/[email protected]/README.tpl.md?source=#version-020, I see the problematic text now rendered correctly.

Hi guys, please take a look at my PR https://github.com/denoland/deno-gfm/pull/96 which solves the yaml issue. (Or at least it tries to -- please let me know if it's not working...

@hashrock, did you fix this with https://github.com/denoland/deno-gfm/pull/72? (I think you have to repeat the keyword to get it to automatically work, e.g. `closes 10, closes 11` instead of `closes 10...

Waiting on https://github.com/denoland/deno-gfm/pull/99, so that this PR is focused purely on YAML, instead of also redoing the testing infrastructure.

@hashrock and @crowlKats, what do you think about this one? On the positive side, it highlights yaml better than we currently do. On the negative side, it might not be...