【问题标题】:Firestore/Firebase not working with Next.jsFirestore/Firebase 不适用于 Next.js
【发布时间】:2022-01-06 20:50:41
【问题描述】:

嘿,你们真的在这里很挣扎。

我正在尝试在我的 Next.js 应用程序中使用 firebase,特别是针对 api。当我在本地构建生产和本地开发时,它运行良好。但是一旦我在 vercel 平台上部署到生产环境,我就会得到一个500 - Internal Server Error。我已经能够将错误范围缩小到使用await getDocs(q) 引起的错误,但不知道如何修复它。

基本上我正在尝试使用来自 firestore 的数据进行动态 api 路由。

firebase.js:

// Import the functions you need from the SDKs you need
import { initializeApp } from "firebase/app";
import { getFirestore } from "firebase/firestore";
import { getStorage } from "firebase/storage";

// TODO: Add SDKs for Firebase products that you want to use
// https://firebase.google.com/docs/web/setup#available-libraries

// Your web app's Firebase configuration
// For Firebase JS SDK v7.20.0 and later, measurementId is optional
const firebaseConfig = {
  apiKey: "<REDACTED_FOR_STACKOVERFLOW>",
  authDomain: "<REDACTED_FOR_STACKOVERFLOW>",
  databaseURL: "<REDACTED_FOR_STACKOVERFLOW>",
  projectId: "<REDACTED_FOR_STACKOVERFLOW>",
  storageBucket: "<REDACTED_FOR_STACKOVERFLOW>",
  messagingSenderId: "<REDACTED_FOR_STACKOVERFLOW>",
  appId: "<REDACTED_FOR_STACKOVERFLOW>",
  measurementId: "<REDACTED_FOR_STACKOVERFLOW>"
};

// Initialize Firebase
const app = initializeApp(firebaseConfig);
// Database
const db = getFirestore();
// Storage
const storage = getStorage(app)

export {
  app,
  storage,
  db
}

/api/users/[name].js:

import { db } from './firebase.js'

export default async function handler(req, res) {
  try {
    const { name } = req.query
    let users = []
    const q = query(collection(db, "users"), where("name", "==", name))
    const querySnapshot = await getDocs(q)
    if (querySnapshot.empty) {
      res.status(404).json({error: "Document does not exist."})
    } else {
      querySnapshot.forEach((doc) => {
        users.push(doc.data())
      })
      res.status(200).json(users)
    }
  } catch(err) {
    res.status(404).json({error: err})
  }
}

package.json:

{
  "name": "app-frontend",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "@headlessui/react": "^1.4.2",
    "@heroicons/react": "^1.0.5",
    "bootstrap": "^4.6.0",
    "classnames": "^2.2.6",
    "next": "11.0.1",
    "firebase": "^9.5.0",
    "postcss-custom-properties": "^8.0.11",
    "postcss-flexbugs-fixes": "^5.0.2",
    "postcss-import": "^14.0.2",
    "postcss-nested": "^5.0.5",
    "postcss-nesting": "^8.0.1",
    "postcss-preset-env": "^6.7.0",
    "react": "17.0.2",
    "react-dom": "17.0.2",
    "react-icons": "^4.2.0",
    "react-markdown": "^6.0.2",
    "react-pro-sidebar": "^0.6.0",
    "react-remark": "^2.0.3",
    "rehype-raw": "^5.1.0",
    "rehype-react": "^6.2.1",
    "remark-html": "^13.0.1",
    "remark-react": "^8.0.0",
    "remark-rehype": "^8.1.0",
    "sass": "^1.35.1",
    "xhr2": "^0.2.1"
  },
  "devDependencies": {
    "autoprefixer": "^10.2.6",
    "eslint": "7.29.0",
    "eslint-config-next": "11.0.1",
    "postcss": "^8.3.5",
    "tailwindcss": "^2.2.4"
  }
}

服务器端的错误是这样开始的: @firebase/firestore: Firestore (9.5.0): INTERNAL UNHANDLED ERROR: Error: ENOENT: no such file or directory, open '/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto'

【问题讨论】:

  • 也许this可以帮助你。
  • 这似乎更针对 Angular,除非 Next.js 中存在我不知道的等效内容? @Ashish
  • 你能分享package.json吗?
  • @ChemiAdel 刚刚添加了它:)
  • @MarioLopez firebase 应该在 package.json 中定义,以便服务器安装它,如果它有效,我会给出答案,不要忘记标记为答案

标签: javascript firebase google-cloud-firestore next.js nextjs-dynamic-routing


【解决方案1】:

问题是依赖项以某种方式安装在本地包 node_modules 中,但未在 package.json 上定义。

您需要在 package.json 中定义它,以便在构建阶段安装它

在项目文件夹上,打开终端并安装它,这样它将被添加到包中:

npm install --save firebase

【讨论】:

  • 哦,很抱歉,这是一个错误的 package.json(在不同的分支上)。让我把正确的。
  • 刚刚更新。谢谢
【解决方案2】:

为此,如果您使用getServerSideProps 中的handler 函数或index.js 中的其他函数,请尝试使用以下代码:

const q = query(collection(getFirestore(app), "users"), where("name", "==", name))

这对我有用。谢谢

【讨论】:

    【解决方案3】:

    将 firebase 降级到 9.4.0 为我解决了确切的问题。我不确定这是否是一个好的修复,但它确实有效。

    【讨论】:

      猜你喜欢
      • 2022-01-10
      • 2020-03-26
      • 2019-11-23
      • 2020-04-04
      • 1970-01-01
      • 2019-12-19
      • 1970-01-01
      • 1970-01-01
      • 2022-06-10
      相关资源
      最近更新 更多