Skip to content

Is Deno support on the horizon? #1307

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

Closed
dadepo opened this issue May 27, 2021 · 3 comments
Closed

Is Deno support on the horizon? #1307

dadepo opened this issue May 27, 2021 · 3 comments

Comments

@dadepo
Copy link

dadepo commented May 27, 2021

Hi there 👋

I would love to use the SDK in a Deno project and it looks like all the conventional methods of using npm packages within Deno does not work.

It would be nice to have deno support support for the SDK, with that there won't be a need to try to use the npm package from Deno.

@google-oss-bot
Copy link

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.

@dadepo dadepo changed the title Is Deno support in the horizon? Is Deno support on the horizon? May 28, 2021
@hiranya911
Copy link
Contributor

There are no specific plans for Deno support at this point (both in Firebase, and within the Google Cloud ecosystem as far as I can tell). But I'd recommend you to file this as a feature request at https://firebase.google.com/support for more visibility within the team.

@akauppi
Copy link

akauppi commented Jul 17, 2022

@hiranya911 Narrowing the Deno/Bun? compatibility gap would likely have a welcome side effect of aligning firebase-admin with where Node itself is going. One example is the fetch API. Node.js 18 has it built-in, and the same implementation is available for Node.js >= 16.5 (if I recall right) with the undici library.

So the limiting factor is Firebase's willingness (customer pressure) to keep supporting Node.js 14.

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

No branches or pull requests

4 participants