i could maybe initialize the logger with an export let

N

neoneyOP•5/16/24, 8:10 PM

then reassign in the middleware?

Nneoney i could maybe initialize the logger with an export let

H

Hello, I’m Allie!•5/16/24, 8:11 PM

That could work?

N

neoneyOP•5/16/24, 8:12 PM

I'll try that

N

neoneyOP•5/16/24, 8:16 PM

one worker shouldnt be reused across requests right?

U

Unsmart•5/16/24, 8:16 PM

A worker can and will be reused

Nneoney one worker shouldnt be reused across requests right?

H

Hello, I’m Allie!•5/16/24, 8:17 PM

It can be, though it is generally tied to a single browser call

U

Unsmart•5/16/24, 8:17 PM

You should never use global scope for request level data (really in any serverless env)

N

neoneyOP•5/16/24, 8:18 PM

H

Hello, I’m Allie!•5/16/24, 8:18 PM

oh wait

H

Hello, I’m Allie!•5/16/24, 8:18 PM

Yeah, that

N

neoneyOP•5/16/24, 8:18 PM

just tryna add some per-request id to my logs

U

Unsmart•5/16/24, 8:18 PM

you can use something like async local storage that you run per request that contains the request id

N

neoneyOP•5/16/24, 8:19 PM

logs are sent from the server

N

neoneyOP•5/16/24, 8:19 PM

and are unfortunately not async

N

neoneyOP•5/16/24, 8:19 PM

unless im misunderstanding

U

Unsmart•5/16/24, 8:19 PM

You can still use ALS

N

neoneyOP•5/16/24, 8:20 PM

as in the import from async_hooks ?

U

Unsmart•5/16/24, 8:20 PM

https://nodejs.org/api/async_context.html

Log with ID is actually the example on the docs for async local storage

N

neoneyOP•5/16/24, 8:20 PM

thought that was node

U

Unsmart•5/16/24, 8:20 PM

cloudflare supports node apis ALS being one of them

N

neoneyOP•5/16/24, 8:20 PM

nice

N

neoneyOP•5/16/24, 8:20 PM

ill try that then

N

neoneyOP•5/16/24, 8:20 PM

thanks

N

neoneyOP•5/16/24, 8:22 PM

im assuming something like this

N

neoneyOP•5/16/24, 8:22 PM

export function middleware(request: NextRequest) {
  const rayId =
    request.headers.get("CF-Ray") ??
    Math.floor(Math.random() * 10000).toString();

  return als.run(rayId, () => NextResponse.next());
}

export function middleware(request: NextRequest) {
  const rayId =
    request.headers.get("CF-Ray") ??
    Math.floor(Math.random() * 10000).toString();

  return als.run(rayId, () => NextResponse.next());
}

export function middleware(request: NextRequest) {
  const rayId =
    request.headers.get("CF-Ray") ??
    Math.floor(Math.random() * 10000).toString();

  return als.run(rayId, () => NextResponse.next());
}

export function middleware(request: NextRequest) {
  const rayId =
    request.headers.get("CF-Ray") ??
    Math.floor(Math.random() * 10000).toString();

  return als.run(rayId, () => NextResponse.next());
}

N

neoneyOP•5/16/24, 8:23 PM

never used als

N

neoneyOP•5/16/24, 8:25 PM

dont think it works unfortunately

N

neoneyOP•5/16/24, 8:26 PM

yeah als.getStore() returns undefined. probably because the middleware doesnt actually run the code, just can alter response/request

N

neoneyOP•5/16/24, 8:35 PM

yeah unfortunately cant find a way to do it. ill use middleware to log requests overall though

N

neoneyOP•5/17/24, 10:56 AM

please tell me node:async_hooks work on pages

N

neoneyOP•5/17/24, 10:57 AM

it works in dev mode, with turbopack

N

neoneyOP•5/17/24, 10:57 AM

but i use webpack for prod

N

neoneyOP•5/17/24, 10:57 AM

and that does

 ⨯ Error: Cannot find module 'node:async_hooks'

⨯ Error: Cannot find module 'node:async_hooks'

 ⨯ Error: Cannot find module 'node:async_hooks'

⨯ Error: Cannot find module 'node:async_hooks'

N

neoneyOP•5/17/24, 10:57 AM

already done

config.plugins.push(
  new webpack.IgnorePlugin({
    resourceRegExp: /^node:async_hooks$/,
  }),
);

config.plugins.push(
  new webpack.IgnorePlugin({
    resourceRegExp: /^node:async_hooks$/,
  }),
);

config.plugins.push(
  new webpack.IgnorePlugin({
    resourceRegExp: /^node:async_hooks$/,
  }),
);

config.plugins.push(
  new webpack.IgnorePlugin({
    resourceRegExp: /^node:async_hooks$/,
  }),
);

N

neoneyOP•5/17/24, 10:57 AM

in my config

Nneoney please tell me node:async_hooks work on pages

J

James•5/17/24, 10:58 AM

ALS is heavily depended on in next.js and next-on-pages

N

neoneyOP•5/17/24, 10:59 AM

N

neoneyOP•5/17/24, 10:59 AM

soo why am i having issues importing it lmaoo

J

James•5/17/24, 10:59 AM

what is it for?

N

neoneyOP•5/17/24, 10:59 AM

well my next-on-pages prooject

N

neoneyOP•5/17/24, 10:59 AM

i use it for logging

N

neoneyOP•5/17/24, 10:59 AM

i removed the ignore plugin and it works in webpack dev i think?

N

neoneyOP•5/17/24, 10:59 AM

yeah

N

neoneyOP•5/17/24, 11:01 AM

but it fails to build

N

neoneyOP•5/17/24, 11:01 AM

page:build: ▲  Failed to compile.
page:build: ▲  node:async_hooks
page:build: ▲  Module build failed: UnhandledSchemeError: Reading from "node:async_hooks" is not handled by plugins (Unhandled scheme).
page:build: ▲  Webpack supports "data:" and "file:" URIs by default.
page:build: ▲  You may need an additional plugin to handle "node:" URIs.

page:build: ▲  Failed to compile.
page:build: ▲  node:async_hooks
page:build: ▲  Module build failed: UnhandledSchemeError: Reading from "node:async_hooks" is not handled by plugins (Unhandled scheme).
page:build: ▲  Webpack supports "data:" and "file:" URIs by default.
page:build: ▲  You may need an additional plugin to handle "node:" URIs.

page:build: ▲  Failed to compile.
page:build: ▲  node:async_hooks
page:build: ▲  Module build failed: UnhandledSchemeError: Reading from "node:async_hooks" is not handled by plugins (Unhandled scheme).
page:build: ▲  Webpack supports "data:" and "file:" URIs by default.
page:build: ▲  You may need an additional plugin to handle "node:" URIs.

page:build: ▲  Failed to compile.
page:build: ▲  node:async_hooks
page:build: ▲  Module build failed: UnhandledSchemeError: Reading from "node:async_hooks" is not handled by plugins (Unhandled scheme).
page:build: ▲  Webpack supports "data:" and "file:" URIs by default.
page:build: ▲  You may need an additional plugin to handle "node:" URIs.

N

neoneyOP•5/17/24, 11:05 AM

what am i missing

N

neoneyOP•5/17/24, 11:14 AM

needs this config to build:

config.plugins.push(
  new webpack.NormalModuleReplacementPlugin(/^node:.*$/, (resource) => {
    resource.request = resource.request.replace("node:", "");
  }),
);

  config.resolve.fallback = {
  ...config.resolve.fallback,
  async_hooks: false,
};

config.plugins.push(
  new webpack.NormalModuleReplacementPlugin(/^node:.*$/, (resource) => {
    resource.request = resource.request.replace("node:", "");
  }),
);

  config.resolve.fallback = {
  ...config.resolve.fallback,
  async_hooks: false,
};

config.plugins.push(
  new webpack.NormalModuleReplacementPlugin(/^node:.*$/, (resource) => {
    resource.request = resource.request.replace("node:", "");
  }),
);

  config.resolve.fallback = {
  ...config.resolve.fallback,
  async_hooks: false,
};

config.plugins.push(
  new webpack.NormalModuleReplacementPlugin(/^node:.*$/, (resource) => {
    resource.request = resource.request.replace("node:", "");
  }),
);

  config.resolve.fallback = {
  ...config.resolve.fallback,
  async_hooks: false,
};

i cant just remove

node:

node:

node:

node: from the import as i reuse the code for a page and a worker, and worker only works when the

node:

node:

node:

node: is specified lol

I'll see if it works in miniflare in a second

N

neoneyOP•5/17/24, 11:15 AM

hell yeah it works

R

Rich•5/17/24, 11:16 AM

Is anybody able to advise on how to configure a Cloudflare Zone so that it doesn't do anything unexpected -- by "unexpected" I mean caches when not explicitly told to cache via Cache-Control headers from our Cloudflare Pages Functions, Workers or Origin servers.

Reading the docs, it seems the default CF cache rules are super complicated, so would love to tear them down so the origin is in complete control.

We have an enterprise account and I'm thinking we should enable "Origin Cache Control", although it's not clear to me exactly how to do this -- if we did enable Origin Cache Control, could there still be default configuration that might catch us out?

RRich Is anybody able to advise on how to configure a Cloudflare Zone so that it doesn...

H

Hello, I’m Allie!•5/17/24, 11:18 AM

For ultimate control, do you mean you want the origin to be able to control Cloudflare's caching of assets separately from browser caching?

i could maybe initialize the logger with an export let

Similar Threads

Similar Threads

Similar Threads