Deno

Deno strives to be browser compatible where possible; that means we use quite a few Web APIs.

There is not much docs for supported Web APIs at the moment and before 1.0 is released that situation must change. Some of APIs and not fully aligned to spec, while others are not fully implemented (#3557). All that knowledge should be written down and presented to end users to avoid multiple question

Hello there! After some experimentation with the mocking API, I discovered that mocked contexts do not provide a mocked Cookies instance. Suppose we wanted to test the following middleware:

// session.ts
// Explicit type annotations omitted for brevity...
export function checkSession(ctx) {
    const maybeSessionId = ctx.cookies.get('sid');
    ctx.assert(maybeSessionId, St

Is your feature request related to a problem? Please describe.

支持自动检测框架的覆盖范围仅仅支持了几个常见前端框架和函数，还可以拓展更多的框架和语言来提升体验

这块的实现是基于配置式的，可以比较轻松拓展一个新框架的支持
https://github.com/TencentCloudBase/cloudbase-framework/blob/master/packages/framework-core/src/detect-frameworks/frameworks.ts

大家可以通过这个快速参与进核心代码的开发当中，目前可以考虑支持的框架和技术有 Hexo, Egg, Koa, Express, Koa , Docker 容器等

• Vue
• React
• V

If you perform C-h f and read the dialog, it can link you to the implementation for that function.

There isn't any technical barrier to do this for JS/TS.

Not sure if this is the correct way to do it, but I wanted to save a cache script I could easily run.

"cache": {
      "desc": "Cache versions and update lock file",
      "cmd": "deno cache server.ts --lock-write",
      "lock": "./lock.json"
}

The result however when running denon cache is an endless loop instead of just executing it once, looks like this:

![Skärmavbild

At the moment you need to do:

# Compile the handler (and fetch dependencies into DENO_DIR).
DENO_DIR=.deno_dir deno fetch hello.ts

# This is the "remapping" step:
cp -R .deno_dir/gen/file/$PWD/ .deno_dir/LAMBDA_TASK_ROOT
# Note: We do the inverse of this operation in bootstrap.

zip lambda.zip -x '.deno_dir/gen/file/*' -r .d