Build issue: Node's own modules are being transpiled, which results in a broken build

[awthwathje]

Build issue: Node's own modules are being transpiled, which results in a broken build

[geelen]

Hi @awthwathje, sorry for the delay in getting back to you, did you manage to get this working at all?

We've had problems with Next plugins in the past: #258

Basically, the whole NextJS ecosystem assumes a full NodeJS runtime, so plugins are usually incompatible with FABs. In this case I think we do need to compile crypto since the NodeJS one isn't accessible within a FAB. I might be wrong, but maybe we can add a browser-compatible crypto shim to this section https://github.com/fab-spec/fab/blob/master/packages/input-nextjs/src/build.ts#L107-L113 ?

How easy is this to reproduce? Does it occur as soon as you spin up a fresh NextJS app and add @auth0/next-auth0?

[loklaan]

I spent a few hours today trying to get @auth0/next-auth0 working. I almost got it there by:

• Adding to shims in input-nextjs/src/build.ts for more native modules (dns, http2, tls)
• Patching the crypto-browserify package with missing crypto exports (generateKeyPair, generateKeyPairSync stub, getCurves).

I ended up giving up on dynamic nextjs 😅, and instead will be just writing dynamic behaviours into custom FAB plugins, because my server.js ended up being over 10mb (unrelated). Thought it might be worth mentioning the above specifics for the next (lol) person though!

[awthwathje]

Hi @awthwathje, sorry for the delay in getting back to you, did you manage to get this working at all?

No, I didn't and the Auth0 SDK had changed recently, and this particular issue is gone now. But it depends on Node.js API and since Workers aren't yet Node.js-compatible, I'm looking for another server-side auth integration.