Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Can We Continue Using Cloud Function v1 Without Changing Import Path After 9/1?

Hi everyone,

I'm seeking clarification regarding the use of Cloud Function v1 after September 1st. Our team currently imports Cloud Function v1 using firebase-functions.

Does anyone know if it's mandatory to change the import path to firebase-functions/v1 after this date? Or can we continue using the existing import path without any issues?

Any insights or official guidance would be greatly appreciated!

Thanks in advance!

Solved Solved
0 3 403
1 ACCEPTED SOLUTION

In that upgrade, which will be a major SDK version, you will need to modify your imports to "v1" to continue using v1.

You are free to update your imports to "v1" in any SDK version published in roughly the last two years to explicitly target V1 and be forwards compatible. There will be no changes to your code as V1 has been the canonical source of truth for some time and the root index.ts is just a reexport from the "v1" directory.

View solution in original post

3 REPLIES 3

In that upgrade, which will be a major SDK version, you will need to modify your imports to "v1" to continue using v1.

You are free to update your imports to "v1" in any SDK version published in roughly the last two years to explicitly target V1 and be forwards compatible. There will be no changes to your code as V1 has been the canonical source of truth for some time and the root index.ts is just a reexport from the "v1" directory.

Does this change affect already deployed v1 functions? Will they stop working?
I was not sure about this point.

@inlined 
Thanks for your support.