🐛 BUG: wrangler pages dev failing with error on Identifier '__cf_cjs' has already been declared

[anywhichway]

Which Cloudflare product(s) does this pertain to?

Pages

What version(s) of the tool(s) are you using?

Wrangler 3.96.0

What version of Node are you using?

N/A

What operating system and version are you using?

Windows 11

Describe the Bug

Observed behavior

X [ERROR] service core:user:bitter-bread-d12c: Uncaught SyntaxError: Identifier '__cf_cjs' has already been declared

    at null.<anonymous> (fn7s4pcgxfq.js:1026)

Expected behavior

App starts

Steps to reproduce

Occurs when the code below is added as a function

Note: You will need to modify line 251 in json-bigint and comment out //case 'null': not valid because your linter also causes a fatal failure on this line

import { PromptRole } from "@llumiverse/core";
import { TogetherAIDriver } from "@llumiverse/drivers";
export async function onRequestPost(ctx) {
    const driver = new TogetherAIDriver({
        apiKey: "<some key>"
    });

    const prompt = [
        {
            role: PromptRole.user,
            content: 'Please, write a short story about winter in Paris, in no more than 512 characters.'
        }
    ]

    const body = await driver.execute(prompt, {
        model:"meta-llama/Meta-Llama-3.1-8B-Instruct-Turbo",
        temperature: 0.6,
        max_tokens: 1024
    });
    return new Response(200,{body:JSON.stringify(body)})
    //return new Response(200,{body:JSON.stringify(prompt)});
}

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

wrangler-2024-12-17_15-58-15_864.log

[Webstablish]

Having the same issue unfortunately.

Uncaught SyntaxError: Identifier '__cf_cjs' has already been declared

In my case it happens when I add a SDK to the project to make API calls to a third party. Commenting out the functions that use the SDK fixes the issue, but breaks the app.

Updating to the latest wrangler version didn't help.

[emily-shen]

Hey thanks for the report! Can I check if you're all using nodejs_compat? And @Webstablish would be super helpful to know which SDK this is happening with.

[Webstablish]

@emily-shen, currently I have this in my wrangler.toml:
compatibility_flags = ["nodejs_compat_v2"]

The SDK I'm using is monday-sdk-js.

[anywhichway]

I dug in a little and found that __cf_cjs looks like it might be dynamically defined by CloudFalre, if so, fix might be to test for undefined first. Here is my compat flag: compatibility_flags = ["nodejs_compat"]

…

On Wed, Dec 18, 2024 at 7:08 AM emily-shen ***@***.***> wrote: Hey thanks for the report! Can I check if you're all using nodejs_compat? And @Webstablish <https://github.com/Webstablish> would be super helpful to know which SDK this is happening with. — Reply to this email directly, view it on GitHub <#7572 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABF2US2V242CZZ5NYO5A4WT2GGFWBAVCNFSM6AAAAABTYYNYS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJRGU3DQOJXGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[anywhichway]

@emily-shen @andyjessop FYI, I tried editing the source of wrangler to make this change. It did not fix the problem.

build5.initialOptions.banner.js += typeof __cf_cjs === "undefined" ? esm_default2`
		function __cf_cjs(esm) {
		  const cjs = 'default' in esm ? esm.default : {};
			for (const [k, v] of Object.entries(esm)) {
				if (k !== 'default') {
					Object.defineProperty(cjs, k, {
						enumerable: true,
						value: v,
					});
				}
			}
			return cjs;
		}
		` : __cf_cjs;

[emily-shen]

Thanks for all the responses so far, sorry for the slow responses over the holiday period :) if you’re able to provide a link to a repo with a minimal reproduction that would be super helpful for us to debug and fix 🧡

[liuhuapiaoyuan]

https://developers.cloudflare.com/workers/runtime-apis/nodejs/streams/

I want to use streams, but the following configurations both result in this error. How should I handle it?

compatibility_flags = ["nodejs_compat_v2"]
compatibility_date = "2024-07-01"

compatibility_flags = ["nodejs_compat"]
compatibility_date = "2024-10-01"

[tori-takashi]

I got a same problem trying to use twitter-api-sdk.
https://www.npmjs.com/package/twitter-api-sdk

import { Hono } from 'hono';
import { handle } from 'hono/cloudflare-pages';
import { env } from 'hono/adapter'
import { Client } from "twitter-api-sdk";

export const app = new Hono();

app.post('api/test', async (c) => {
const { X_BEARER_TOKEN } = env<{
        X_BEARER_TOKEN: string;
    }>(c)
const XClient = new Client(X_BEARER_TOKEN as string);
});

export const onRequest = handle(app);

on wrangler 3.100.0.

When I remove const XClient = new Client(X_BEARER_TOKEN as string); then no error displayed.

[devmax214]

I got the same error using i18next-fs-backend and [email protected].
My configs

compatibility_flags = [ "nodejs_compat" ]
compatibility_date = "2024-10-01"

Also in my case, when I used the function eval, the error was presenting.
After I replaced the eval it fixed. But when I add the module i18next-fs-backend, the error is showing again.

[devmax214]

I changed the wrangler cli source, so I replaced __cf_cjs with globalThis.__cf_cjs.

...
build5.initialOptions.banner.js += esm_default2`
	globalThis.__cf_cjs = function (esm) {
        const cjs = 'default' in esm ? esm.default : {};
        for (const [k, v] of Object.entries(esm)) {
            if (k !== 'default') {
                Object.defineProperty(cjs, k, {
                    enumerable: true,
                    value: v,
                });
            }
        }
        return cjs;
    };
		`;
  build5.onLoad(
    { filter: /.*/, namespace: REQUIRED_UNENV_ALIAS_NAMESPACE },
    ({ path: path70 }) => {
      return {
        contents: esm_default2`
		import * as esm from '${path70}';
		module.exports = globalThis.__cf_cjs(esm);
	`,
        loader: "js"
      };
    }
  );
...

It works for me.
@emily-shen please check at next version. Thanks.