Jeremy Kreutzbender

Results 8 comments of Jeremy Kreutzbender

@christophemenager @Zenfection1412 It happens when you don't have `selectors` defined in your config file. I just ran into the same thing.

@shuding Can this be-reopened? I'm running into this same issue and we run our Next.js project in a Docker container in Kubernetes so there is 0% chance the code will...

I did some debugging and re-created the issue in this repository https://github.com/jer-k/middleware-debug On the `main` branch, everything works as expected * https://github.com/jer-k/middleware-debug/blob/main/src/middleware.ts * I imported lodash, used it, added the...

Looks like I was able to resolve this. After adding the telemetry output I was able to see this ``` [telemetry] { "eventName": "NEXT_EDGE_ALLOW_DYNAMIC_USED", "payload": { "file": "private-next-root-dir/src/middleware.ts", "config": {...

@grantmagdanz You have to include the `config` with `unstable_allowDynamic` in your `middleware` file to get the telemetry to print out. As long as there is anything in there, it'll print....

@shinyuna Try ` "**/.pnpm/**/node_modules/lodash-es/*.js"` you need to capture the `../../node_modules` at the start of `../../node_modules/.pnpm/[email protected]/node_modules/lodash-es/_root.js` which `**` will match

> Edge Runtime is not an infra, and it will be the runtime for Next.js middleware, and pages with export const runtime = 'edge', no matter where you host the...

I ended up having to solve this too and none of the other solutions seemed to work. I'm unsure if something changed since the previous solutions were posted here. Importantly,...