-
Notifications
You must be signed in to change notification settings - Fork 203
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
6.0.0 Property 'region' does not exist on type 'typeof import #1614
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
I just went through the recent code changes to the repo and saw that the default has changed. So updating my imports to Has this been documented anywhere? Are we now able to use |
where is the changelog mentioned in #1606 |
import functions from 'firebase-functions' Did the trick for me. |
this should have been mentioned in the changelog |
For others who land here from search, I had a similar error when trying to deploy cloud functions: firebase cloud functions Property 'runWith' does not exist on type 'typeof... The import from /v1 change described above helped, but I also had to downgrade firebase-functions to 5.0 from 6.0: |
Related issues
No - checked ChangeLog too
[REQUIRED] Version info
upgrade from ^5.1.1 to ^6.0.0
node:
v20.15.0
firebase-functions:
^6.0.0
firebase-tools:
13.17.0
firebase-admin:
[REQUIRED] Test case
all my cloud functions were setup to run in region region("europe-west1")
I did a
firebase deploy --only functions
and saw the prompt tonpm install --save firebase-functions@latest
I then redeployed my cloud functions and got errors in two cloud functions stating that:
error TS2339: Property 'region' does not exist on type 'typeof import("/home/user/development/app/functions/node_modules/firebase-functions/lib/v2/index")'
[REQUIRED] Steps to reproduce
[REQUIRED] Expected behavior
It should deploy in the same way as previously
[REQUIRED] Actual behavior
error on deployment
Were you able to successfully deploy your functions?
not since upgrading to 6.0.0
The text was updated successfully, but these errors were encountered: