This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Getting @firebase/firestore: Firestore (9.6.1): INTERNAL UNHANDLED ERROR in vercel deployment #32527
Labels
please add a complete reproduction
The issue lacks information for further investigation
What version of Next.js are you using?
12.0.7
What version of Node.js are you using?
v16.9.1
What browser are you using?
Opera, Chrome
What operating system are you using?
Windows
How are you deploying your application?
Vercel
Describe the Bug
I deployed my project with Vercel. But Im getting this error in my [id].js file.
2021-12-15T06:17:23.492Z 9a841814-7b90-4455-ae7d-2482a27527bb ERROR [2021-12-15T06:17:23.492Z] @firebase/firestore: Firestore (9.6.1): 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' at Object.openSync (fs.js:462:3) at Object.readFileSync (fs.js:364:35) at fetch (/var/task/node_modules/protobufjs/src/root.js:172:34) at Root.load (/var/task/node_modules/protobufjs/src/root.js:206:13) at Root.loadSync (/var/task/node_modules/protobufjs/src/root.js:247:17) at Object.loadProtosWithOptionsSync (/var/task/node_modules/@grpc/proto-loader/build/src/util.js:66:29) at loadSync (/var/task/node_modules/@grpc/proto-loader/build/src/index.js:194:31) at loadProtos (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:14500:31) at newConnection (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:14522:20) at OnlineComponentProvider.createDatastore (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:18436:28) 2021-12-15T06:17:23.493Z 9a841814-7b90-4455-ae7d-2482a27527bb ERROR Unhandled Promise Rejection {"errorType":"Runtime.UnhandledPromiseRejection","errorMessage":"Error: ENOENT: no such file or directory, open '/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto'","reason":{"errorType":"Error","errorMessage":"ENOENT: no such file or directory, open '/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto'","code":"ENOENT","errno":-2,"syscall":"open","path":"/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto","stack":["Error: ENOENT: no such file or directory, open '/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto'"," at Object.openSync (fs.js:462:3)"," at Object.readFileSync (fs.js:364:35)"," at fetch (/var/task/node_modules/protobufjs/src/root.js:172:34)"," at Root.load (/var/task/node_modules/protobufjs/src/root.js:206:13)"," at Root.loadSync (/var/task/node_modules/protobufjs/src/root.js:247:17)"," at Object.loadProtosWithOptionsSync (/var/task/node_modules/@grpc/proto-loader/build/src/util.js:66:29)"," at loadSync (/var/task/node_modules/@grpc/proto-loader/build/src/index.js:194:31)"," at loadProtos (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:14500:31)"," at newConnection (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:14522:20)"," at OnlineComponentProvider.createDatastore (file:///var/task/node_modules/@firebase/firestore/dist/index.node.mjs:18436:28)"]},"promise":{},"stack":["Runtime.UnhandledPromiseRejection: Error: ENOENT: no such file or directory, open '/var/task/node_modules/@firebase/firestore/dist/src/protos/google/firestore/v1/firestore.proto'"," at process.<anonymous> (/var/runtime/index.js:35:15)"," at process.emit (events.js:326:22)"," at processPromiseRejections (internal/process/promises.js:209:33)"," at processTicksAndRejections (internal/process/task_queues.js:98:32)"]} Unknown application error occurred
Im using getServerSideProps in [id].js file so i think im getting that error because of it. But in local dev mode everything works without any issue.
My getServerSideProps codes
Expected Behavior
I just want to learn why Im getting this error and How can I fix it.
To Reproduce
The text was updated successfully, but these errors were encountered: