-
Notifications
You must be signed in to change notification settings - Fork 64
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
ERR_REQUIRE_ESM error when starting emulator ui #1014
Comments
The same issue with a fresh install of Ubuntu 22.04.4 LTS. Tested Node 16, 18 and 20 LTS. |
I made some changes to the UI recently which changed the output from js to mjs - try installing a version prior to 13.5.1 and see if that fixes the issue https://github.com/firebase/firebase-tools/releases/tag/v13.5.1 |
https://github.com/firebase/firebase-tools/releases/tag/v13.5.0 fixes the issue. |
I have 13.6.0 and facing the same issue, should I downgrade? |
Try downgrading and report the results, I can't reproduce on my linux
version but more information is helpful
…On Wed, Mar 27, 2024 at 2:09 PM Moses Gameli ***@***.***> wrote:
I have 13.6.0 and facing the same issue, should I downgrade?
—
Reply to this email directly, view it on GitHub
<#1014 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZKGOHSY3YILS6HWXBXOBJLY2MYRZAVCNFSM6AAAAABCWHS7PCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTHE4TKMBQGI>
.
You are receiving this because you were mentioned.Message ID:
<firebase/firebase-tools-ui/issues/1014/2023995002 <(202)%20399-5002>@
github.com>
|
Same here, downgrading to 13.5.0 solved the issue. |
Downgrading from 13.8.0 to 13.5.0 resolved the issue for me as well. |
running into this on macOS 14.6.1 as well:
and in
Something is clearly broken here - and downgrading isn't really a solution - can someone please look at this? |
I have the exact problem. Did you manage to fix it. |
Same issue here, also on macOS 14.6.1.
Downgrading does work, but reports the following warnings:
Additionally, this warning shows up in the function logs:
It would be great to see some movement on a proper fix as opposed to a risky workaround. |
I am also having this issue on Ubuntu 24.04.1 LTS | |
At least on Mac, removing the broken curl-installed latest version (13.19.0) with |
@kwight thanks, it fixed my error |
@kwight I didn't need to uninstall anything, but it appears that this issue is indeed fixed in 13.20.x 🥳 |
@Genyus , i try get my firebase emulator on Docker work as code show below
The same error present
Config:
|
@neviaumi Maybe try the approach suggested by @kwight above in your Docker config and install with npm instead of curl?
|
@Genyus Thanks for suggestion :) I do fix it as you suggested. Using Npm instead of auto installation script. Here is working docker file
|
This is making |
I'm having the same issue on the latest version, 13.22.1, on MacOS, installed using the installation script from Installing via I wonder if it's something to do with the node environment it runs in, because I also noticed in ui-debug.log that when it was having an error, the end of the log said "Node.js v18.5.0" which is not a version I can find installed on my system... (at least not via nvm or asdf... I don't think MacOS has a system version of node preinstalled, does it?) |
Occurring for me on MacOS as well. Installing |
Only thing that worked,
In our case, we were not able to install firebase-tools using npm. The script version was getting installed, but it has some known bug with latest release. |
###ASAP -- i have a project submission next day please (Any one 🙏) |
Exact same issue here. @kwight thanks, your solution fixed it for me. |
Describe the bug
When I start the emulators with emulators start command, all, but ui starts. This is the error log:
I don't know where node v18.5.0 comes from, I haven't found this version on my PC, my node version is 21.1.0, which is available in $PATH. Also, once I could see v20 after
nvm use v20...
and deleting firebase cache, but the next run it was v18.5.0 again.To Reproduce
Steps to reproduce the behavior:
firebase emulators:start
Expected behavior
It should be running.
Desktop:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: