Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to compile #290

Open
appalliance opened this issue May 10, 2024 · 1 comment
Open

Failed to compile #290

appalliance opened this issue May 10, 2024 · 1 comment

Comments

@appalliance
Copy link

appalliance commented May 10, 2024

I follow the steps in the [Integrate Firebase with a Next.js app](https://firebase.google.com/codelabs/firebase-nextjs#0). Everything works fine up to and including Step 5: Start the Hosting emulator. I get the "All emulators ready! It is now safe to connect your app." message. When I navigate to http://localhost:5000, instead of the home page, I get an error message:

./node_modules/farmhash/build/Release/farmhash.node
Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Here is the stack trace:

./node_modules/google-gax/build/src/streamingRetryRequest.js
./node_modules/google-gax/build/src/streamingCalls/streaming.js
./node_modules/google-gax/build/src/fallback.js
./node_modules/@google-cloud/firestore/build/src/index.js
./node_modules/firebase-admin/lib/app/firebase-namespace.js
./node_modules/firebase-admin/lib/default-namespace.js
./node_modules/firebase-admin/lib/index.js
./src/lib/firebase/firebase.js
./src/lib/firebase/firestore.js
./src/components/RestaurantListings.jsx

I reported this error to the firebase-tools team but they believe it is an application error.

firebase-debug.log

@appalliance
Copy link
Author

Another thought: could this be a simple tooling issue? Am I missing a loader that is needed for this project? Unfortunately, the error message doesn't provide enough insights into what tooling is missing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant