Thanks for stopping by to let us know something could be better!
Bug: Firestore Node.js v8.2.0 prevents deploying new Cloud Run revisions (ERR_PACKAGE_PATH_NOT_EXPORTED)
After upgrading to @google-cloud/firestore@8.2.0, new Cloud Run revisions cannot be deployed.
The container fails during startup and exits immediately, causing the deployment to fail and blocking new code rollout.
This appears to be a deployment-blocking regression introduced in 8.2.0.
Environment details
- OS: Linux (Google Cloud Run container runtime)
- Node.js version: 22.x
- npm version: (Cloud Build / container default)
@google-cloud/firestore version: 8.2.0
Steps to reproduce
-
Use a Cloud Run service running Node.js 22.
-
Upgrade dependency to @google-cloud/firestore@8.2.0.
-
Deploy a new Cloud Run revision.
-
Deployment fails because the container exits during startup with:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './build/src' is not defined by "exports" in
/workspace/node_modules/@google-cloud/firestore/package.json
Cloud Run logs show:
- “Provided module can't be loaded.”
- “Could not load the function, shutting down.”
- Container exits with code 1
Expected behavior
New Cloud Run revisions should deploy successfully, as they do with Firestore versions prior to 8.2.0.
Impact
- 🚫 Blocks deployment of new code
- 🚫 CI/CD pipelines fail
- 🚫 No safe rollout path without downgrading Firestore
Workaround
Pin @google-cloud/firestore to a version before 8.2.0. In our case, 8.0.0 works.
Additional context
The error references an internal path (./build/src) that is not exported, suggesting a packaging or exports map issue introduced in this release.
Thanks for stopping by to let us know something could be better!
Bug: Firestore Node.js v8.2.0 prevents deploying new Cloud Run revisions (
ERR_PACKAGE_PATH_NOT_EXPORTED)After upgrading to
@google-cloud/firestore@8.2.0, new Cloud Run revisions cannot be deployed.The container fails during startup and exits immediately, causing the deployment to fail and blocking new code rollout.
This appears to be a deployment-blocking regression introduced in
8.2.0.Environment details
@google-cloud/firestoreversion: 8.2.0Steps to reproduce
Use a Cloud Run service running Node.js 22.
Upgrade dependency to
@google-cloud/firestore@8.2.0.Deploy a new Cloud Run revision.
Deployment fails because the container exits during startup with:
Cloud Run logs show:
Expected behavior
New Cloud Run revisions should deploy successfully, as they do with Firestore versions prior to 8.2.0.
Impact
Workaround
Pin
@google-cloud/firestoreto a version before 8.2.0. In our case, 8.0.0 works.Additional context
The error references an internal path (
./build/src) that is not exported, suggesting a packaging orexportsmap issue introduced in this release.