Unexpected token '!'

[Eddie344]

Environment

• Operating System: Darwin
• Node Version: v20.11.0
• Nuxt Version: 2.17.3
• CLI Version: 3.10.0
• Nitro Version: 2.8.1
• Package Manager: yarn@1.22.19
• Builder: webpack
• User Config: -
• Runtime Modules: -
• Build Modules: -

Reproduction

Usual nuxt 2 project with @nuxtjs/composition-api v0.31.0

I'm going through nuxt bridge migration guide.
I try to set anything inside bridge field inside nuxt.config, for example:

bridge {
  typescript: true
}

When bridge: false, everything is ok

Describe the bug

Additional context

No response

Logs

No response

[Eddie344]

Also I tried other node js versions: 16, 18

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v2-bridge
👉 https://codesandbox.io/p/github/nuxt/starter/v2-bridge-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[wattanx]

Maybe it is the same as #1063.

[Eddie344]

I found the reason: the problem was in my server middleware for recaptcha

import { readBody } from 'h3';
import { ofetch } from 'ofetch';

const SECRET_KEY = process.env.RECAPTCHA_PRIVATE_KEY;

export default async (req, res) => {
  res.setHeader('Content-Type', 'application/json');

  // eslint-disable-next-line no-unreachable
  try {
    const { token } = await readBody({ node: { req }, method: 'POST' });

    if (!token) {
      res.end(
        JSON.stringify({
          success: false,
          message: 'Invalid token',
        }),
      );
      return;
    }

    const response = await ofetch(
      `https://www.google.com/recaptcha/api/siteverify?secret=${SECRET_KEY}&response=${token}`,
      {
        method: 'POST',
      },
    );

    res.end(
      JSON.stringify({
        success: response.success,
        response,
      }),
    );
  } catch (error) {
    console.error(error);
    res.end(
      JSON.stringify({
        success: false,
        message: 'Internal error',
        error,
      }),
    );
  }
};

I have not figured out exactly what the problem is, just turn off this file

[kyumoon]

I found the cause.
import http from "node:http" doesn't work properly with webpack + bridge.
Before switching to vite, we can use path-package to fix it

-import http from 'node:http';
-import https from 'node:https';
+import http from 'http';
+import https from 'https';