Simon Lecoq

The `Deno.PermissionOptionsObject` actually already allows the "inherit" (both at granular and global levels), and supports booleans too. The only thing is that maybe "true" should be replaced by "inherit" by...

I started some work about this, but unfortunately I'm blocked for now because of upstream issues Blockers: - https://github.com/denoland/deno/issues/29509 Blockers for using `--import` permissions for ``: - https://github.com/denoland/deno/issues/29503 - https://github.com/denoland/deno/issues/27050...

Opened upstream: - https://github.com/denoland/deno/pull/29610 This should be enough to unblock (https://github.com/denoland/deno/issues/29503 is not actually required)

It is technically already (partially) possible, though there's an open issue for that: - #57 In JS, dictionnaries are ordered so when the parser will build the document, it'll add...

I don't want to push the `http` scope towards a `dom` scope, but I do think it can be useful for people that works with dom libraries. Mainly, maintainers who...

Yes it seems so I'm not entirely sure why (I'm a bit rusted on node + TS ecosystem since I mainly use TS runtimes now) but after generating types declarations...

It's when you curl the meta.json ``` curl https://jsr.io/@luca/test/meta.json 404 - Not Found ``` ``` curl https://jsr.io/@luca/pi/meta.json { "scope": "luca", "name": "pi", "versions": { "1.2.0": {}, "1.0.0": {}, "1.1.0": {}...

Just getting package metadata It's just the https://jsr.io/docs/api#package-metadata doesn't precise that the package should have been published with at least one version > ### Package metadata > Package metadata refers...

Hi ! Thanks a lot for the great, detailed and clean write-up, it was very pleasing to read. I think 2 and 3 should indeed be :where matcha is moving...

Hi ! I'll look into it in the near future, it'd also reduce the overall build size too so that's definitely a good change !