How can I set global environment variables accessable on the env property?

service-worker-mock version 2.0.5 changed the signature for trigger('fetch', request) to return a single Response instead of Response[]. As a result, the type definitions are out of sync depending which version you are running.

It appears that cloudflare-worker-mock has a dependency on @udacity/types-service-worker-mock, which is not listed as a dependency in the package.json.

Requiring the module in JS gives this error:

Error: Cannot find module '@udacity/types-service-worker-mock/global'

Thanks for all your work on this!

Hi, you might consider switching from service-worker-mock to edge-mock (which I've just built).

Just a suggestion, feel free to close this if you like.

A few advantages of edge-mock:

1. service-workers the project which service-worker-mock is a part of is no longer maintained.
2. edge-mock provides support for KV store mocking out-of-the-box
3. edge-mock properly supports ArrayBuffer and ReadableStream which service-worker-mock do does not
4. edge-mock has close to 100% test coverage and is written in typescript.
5. All the implementations provided by edge-mock are fully compliant with the types they implement in typescript.

microsoft/TypeScript-DOM-lib-generator#729 has been resolved, which means #5 can be reverted, when the new typings are available upstream. Probably the next TS point release.

Hi!

Love that someone's built out types for workers.

In the definition for CloudflareWorkerKV located here: https://sourcegraph.com/github.com/udacity/cloudflare-typescript-workers/-/blob/packages/types-cloudflare-worker/src/global.ts#L384

there isn't a function definition for listing keys documented here: https://developers.cloudflare.com/workers/reference/storage/listing-keys/

Should be a super simple addition.

I'm trying to test code that does something like crypto.subtle.digest('MD5', body). However, when I run the test, I get the error ReferenceError: crypto is not defined.

Do the mocks need to be augmented to add support for the crypto API?

Related:

• https://developer.mozilla.org/en-US/docs/Web/API/Web_Crypto_API
• https://developers.cloudflare.com/workers/reference/apis/web-crypto/

I have some test code that sets up a mock response like this:

fetchMock.mockResponse('', {
  headers: {
    'Content-Type': 'text/html'
  },
  status: 404
})

However, I noticed that my tests that were inspecting the Content-Type response header weren't behaving as expected. While debugging, I noticed that after I cloned the Response object with new Response(response.body, response), the resulting object did not have the response header. This seems to be the recommended way to clone the Response so that headers can be mutated, but I'm wondering if there's a way to get the test to behave the same way as Cloudflare does (keeping the headers in this circumstance).

Here's how you can see the issue in action if you run this code within a test:

const originalResponse = new Response('', {
  headers: {
    TestKey: 'TestValue'
  }
})
console.log('original', originalResponse.headers.get('TestKey'))

const clonedResponse = new Response(originalResponse.body, originalResponse)
console.log('cloned', clonedResponse.headers.get('TestKey'))

One possible workaround is to add code that does response.clone() when running a test instead of new Response(response.body, response), but that's not idea since it clutters the actual code. You can't use response.clone() in production because you still can't mutate the headers of the cloned Response object when you run the code in a real Cloudflare Worker.

Is there any way to get the test to behave more like Cloudflare Workers does?

The issue is with the list method signature (which is actually correct in the docblock above it).
NAMESPACE.list({prefix?: string, limit?: number, cursor?: string})

If I call the list method like this:
KVNAMESPACE.list('my_prefix').then((mylist) => {...
then it compiles but during execution it thorows the following error:
TypeError: Failed to execute 'list' on 'KvNamespace': parameter 1 is not of type 'ListOptions'.

If I call the list method like this:
KVNAMESPACE.list({prefix: 'my_prefix'}).then((mylist) => {...
then my code won't compile becasue I get:
Error:(35, 25) TS2345: Argument of type '{ prefix: string; }' is not assignable to parameter of type 'string'.

only if i do:

// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore
KVNAMESPACE.list({ prefix: prefix }).then((mylist) => {...

then it will run.

In the actual KV API, KV.delete is async. In the definitions file, it is not. Using KV in a TypeScript project generates incorrect errors using the current definitions file.

To fix it, change R653 in the above reference to

delete(key: string): Promise<void>;

Hey, folks!

Given that Cloudflare seems to actively support typings for workers now: https://github.com/cloudflare/workers-types, do you have any plans on syncing/migrating to the "official" typings?

Thanks for amazing work here btw :)