Skip to content

Support types for NodeJS 12 #1100

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
sk- opened this issue Nov 30, 2020 · 4 comments
Closed

Support types for NodeJS 12 #1100

sk- opened this issue Nov 30, 2020 · 4 comments
Assignees

Comments

@sk-
Copy link
Contributor

sk- commented Nov 30, 2020

[REQUIRED] Step 2: Describe your environment

  • Firebase SDK version: 9.4.1
  • Firebase Product: admin
  • Node.js version: 12

[REQUIRED] Step 3: Describe the problem

Now that cloud functions support for NodeJS 12 is at the GA level, the type dependencies should reflect that, so instead of depending on the types for Node 10, it should depend in either the types for node 10 or the types for node 12.

See

"@types/node": "^10.10.0",

That line should probably be changed to something like:

"@types/node": "^10.10.0 || ^12"

I'm not sure though if that dependency really needs to be a runtime dependency or it it could be moved to a dev dependency.

Steps to reproduce:

What happened? How can we make the problem occur?
This could be a description, log/console output, etc.

Relevant Code:

// TODO(you): code here to reproduce the problem
@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.

@hiranya911
Copy link
Contributor

I think we can make it a dev dependency (and is probably the right course of action). I'll take a look in the coming days.

@swftvsn
Copy link

swftvsn commented Feb 24, 2021

This has proven to be a problem for us also. Please consider to work on it.

@nikhilag
Copy link
Contributor

I believe this issue has been fixed in #1258

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

6 participants