主页 / coding / 问题 / 79531750
Accepted
Europa
Asked: 2025-03-25 01:30:40 +0800 CST

Next.js 15.2.3 服务器 api get 给出“route.ts 具有无效的 GET 导出：类型“{params？：{monitorId？：string | undefined;} | undefined;}”不是”

  • 772

我有一个 Next.js 15.2.3 服务器 api 路由，它接收monitorId并在数据库中返回结果。

Next.js 15.2.3 服务器 api 路由路径为 app/(private)/monitors/[monitorId]/api-get-monitor/route.ts。

// app/(private)/monitors/[monitorId]/api-get-monitor/route.ts

import { NextRequest, NextResponse } from "next/server";
import { sql } from "@/app/lib/db";
import { loginIsRequiredServer } from "@/app/lib/loginIsRequiredServer";
import { getServerSession } from "next-auth";
import { authConfig } from "@/app/lib/auth";

// Use the built-in RequestContext type
export async function GET(request: NextRequest, context: { params?: { monitorId?: string } }) {
  // Ensure params exist
  if (!context.params?.monitorId) {
    return NextResponse.json({ message: "Missing monitor ID" }, { status: 400 });
  }

  const { monitorId } = context.params;

  console.error(`api-get-monitor · Get Monitor: ${monitorId}`);

  // Session check
  await loginIsRequiredServer();
  const session = await getServerSession(authConfig);
  if (!session) {
    return NextResponse.json({ message: "Unauthorized" }, { status: 401 });
  }

  try {
    // Query the database for monitor details using the monitorId
    const res = await sql(
      `SELECT monitor_id, title, what_to_monitor, url_to_monitor, escalation_email_on, 
      escalation_email_to, check_frequency, last_checked_timestamp, is_offline, offline_datetime
      FROM u_monitors_index WHERE monitor_id = $1`,
      [monitorId]
    );

    if (res.rows.length === 0) {
      return NextResponse.json({ message: "Monitor not found" }, { status: 404 });
    }

    return NextResponse.json({ data: res.rows[0] });
  } catch (error) {
    console.error("get-monitor · Error getting:", error);
    return NextResponse.json({ message: "Error getting monitor" }, { status: 500 });
  }
}

这在本地有效，但当我将其部署到 Google Cloud Run 时出现以下错误

   Linting and checking validity of types ...
Failed to compile.
app/(private)/monitors/[monitorId]/api-get-monitor/route.ts
Type error: Route "app/(private)/monitors/[monitorId]/api-get-monitor/route.ts" has an invalid "GET" export:
  Type "{ params?: { monitorId?: string | undefined; } | undefined; }" is not a valid type for the function's second argument.
    Expected "Promise<any>", got "{ monitorId?: string | undefined; } | undefined".
      Expected "Promise<any>", got "undefined".
Next.js build worker exited with code: 1 and signal: null

这不params就是 Next.js 传递的一个对象吗，不是一个异步操作吗？我不明白这里的错误。

next.js

1 个回答

  1. Best Answer

    您在生产构建期间收到该错误，因为从 NextJS 15 开始，params 现在是一个承诺，而不是像 NextJS 15 之前的版本那样是一个同步对象。您所要做的就是调整您的类型以使 params 成为一个承诺对象。

    export async function GET(request: NextRequest, context: { params: Promise<{ monitorId: string }> }) {

  const monitorId = (await context.params).monitorId;

  // Ensure params exist
  if (!monitorId) {
    return NextResponse.json({ message: "Missing monitor ID" }, { status: 400 });
  }

  console.error(`api-get-monitor · Get Monitor: ${monitorId}`);

  // Session check
  await loginIsRequiredServer();
  const session = await getServerSession(authConfig);
  if (!session) {
    return NextResponse.json({ message: "Unauthorized" }, { status: 401 });
  }

  try {
    // Query the database for monitor details using the monitorId
    const res = await sql(
      `SELECT monitor_id, title, what_to_monitor, url_to_monitor, escalation_email_on, 
      escalation_email_to, check_frequency, last_checked_timestamp, is_offline, offline_datetime
      FROM u_monitors_index WHERE monitor_id = $1`,
      [monitorId]
    );

    if (res.rows.length === 0) {
      return NextResponse.json({ message: "Monitor not found" }, { status: 404 });
    }

    return NextResponse.json({ data: res.rows[0] });
  } catch (error) {
    console.error("get-monitor · Error getting:", error);
    return NextResponse.json({ message: "Error getting monitor" }, { status: 500 });
  }
}

    以下是文档的参考： https://nextjs.org/docs/app/api-reference/file-conventions/route#context-optional

    • 2

相关问题