Luca Casonato

Our workaround for this was emitting both the `.js` and `.d.ts` files into a separate directory, but this has other issues (namely `import.meta.url` is now wrong for users, e.g https://github.com/jsr-io/jsr/issues/477)....

This error looks to be solved in 1.4: ``` fetch('https://pictures.vwe.nl').then(console.log) Promise { } Response { _bodySource: ReadableStream { locked: false }, _stream: null, url: "https://pictures.vwe.nl", statusText: "Forbidden", status: 403, headers:...

Depends on the size of value. `ceil((value size + key size of all mutations in the atomic operation) / 1024)` So at least two, but up to 1600 (max size...

@csvn Support for the `with` keyword was only released a couple days ago in the CLI. Deploy just hasn't caught up yet. It'll start working on Deploy soon

Partial duplicate of #2297?

> or running deno info on top of each file, which can be problematic We already do this.

Reopening, this is still relevant.

Yes I agree. I don't think we should make them objects. Let's update the style guide

xpost: #3878

You can not sandbox JS code from within JS. For all intents and proposes, the entire JS sandbox must be untrusted.