[middlewares] globalThis and globalThis.CryptoKey is missing

[panva]

What version of Next.js are you using?

12.0.1

What version of Node.js are you using?

v14.18.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Both Vercel and next dev

Describe the Bug

Testing a universal JOSE (JWT/JWK/etc) library on Middlewares I've encountered an issue where the CryptoKey constructor is not exposed via globalThis.CryptoKey.

This is the case for all browsers, Deno, and Cloudflare Workers runtimes but not for Middlewares deployed via vercel or running via next dev.

Not having access to this constructor prohibits my particular library from validating user inputs.

In next dev globalThis.CryptoKey is missing, in vercel.com runtime globalThis is missing completely.

Expected Behavior

globalThis, globalThis.CryptoKey, and CryptoKey are exposed both running via next dev or deployed via vercel.com

To Reproduce

Create a middleware like so, both in development as well as vercel.com, observe the failures are there and also, different.

export default async function middleware(req, ev) {
  try {
    if (typeof CryptoKey === 'undefined') {
      throw new Error('CryptoKey is missing')
    }
    if (typeof globalThis === 'undefined') {
      throw new Error('globalThis is missing')
    }
    if (!globalThis.CryptoKey) {
      throw new Error('globalThis.CryptoKey is missing')
    }
    return new Response(JSON.stringify({}), { status: 200 });
  } catch (err) {
    return new Response(JSON.stringify({ error: err.stack }), { status: 400 });
  }
}

[panva]

Note that CryptoKey's WebIDL defines CryptoKey as exposed via globals. See https://w3c.github.io/webcrypto/#cryptokey-interface

[javivelasco]

We're bringing in globalThis to expose the global env, PR coming.

[panva]

@javivelasco globalThis is just one portion, but a great start nontheless!

[NateRadebaugh]

Looks like globalThis made it into v12.0.3-canary.3

• Edge Functions: expose globalThis #30877

Does CryptoKey come for free or another PR needed for that?

[panva]

It does not come for free ;)

[javivelasco]

We are adding it in the next canary

[panva]

export async function middleware(req, ev) {
  return new Response(JSON.stringify({
    globalThisPresent: typeof globalThis !== 'undefined',
    CryptoKeyInGlobalThis: typeof globalThis !== 'undefined' && typeof globalThis.CryptoKey !== 'undefined',
    CryptoKey: typeof CryptoKey !== 'undefined'
  }), { status: 200 });
}

State as of 12.0.3-canary.9

next dev

{
  "globalThisPresent": true,
  "CryptoKeyInGlobalThis": false,
  "CryptoKey": false
}

Edge Functions

{
  "globalThisPresent": false,
  "CryptoKeyInGlobalThis": false,
  "CryptoKey": false
}

[panva]

#31193 (comment)

This is not fixed on Edge Functions still as per my previous comment in this issue.

[Kikobeats]

@panva right, no problem. A new runtime version should be released paired with the next canary, let me ping you when is done 🙂

[panva]

Right. But the release of 12.0.3 didnt align globalThis on edge functions so i'm wondering how this works...

[panva]

Same with the new canary - locally its good now, on vercel.com - not. https://my-next-app-panva.vercel.app

[ijjk]

@panva this has now been rolled to stable on Vercel, please re-deploy and give a try!

[NateRadebaugh]

LGTM from the prior URL:

[panva]

Yup!

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.