Skip to content
This repository was archived by the owner on Mar 19, 2026. It is now read-only.
This repository was archived by the owner on Mar 19, 2026. It is now read-only.

Deprecation warnings from node-fetch and rimraf in downstream consumers #925

Closed
#931
Closed
Deprecation warnings from node-fetch and rimraf in downstream consumers#925
#931
Assignees
quirogas
Labels
priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: processA process-related concern. May include testing, release, or the like.

Description

@sherman-yang
sherman-yang
opened on Mar 7, 2026

When consumers install libraries that transitively depend on gaxios (like google-auth-library), they see npm deprecation warnings:

npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported

These come from the node-fetch and rimraf dependencies. Moving gaxios to the native Node 18+ fetch API removes the node-fetch dependency tree and eliminates these transitive warnings for all consumers.

Activity

  1. benmccann commented on Mar 8, 2026

    @benmccann
    benmccann
    on Mar 8, 2026
    Contributor

    rimraf is already removed but consumers are pinned to old versions of gaxios, so the pinning should be removed. For example:

    google-cloud-node-core/packages/google-auth-library-nodejs/package.json

    Line 26 in 7feb4c8

    "gaxios": "7.1.3",

  2. benmccann commented on Mar 8, 2026

    @benmccann
    benmccann
    on Mar 8, 2026
    Contributor

    Looks like there's a PR for it: #922

  3. AviVahl commented on Mar 10, 2026

    @AviVahl
    AviVahl
    on Mar 10, 2026

    They've actually pinned the dependency version right before the new gaxios was released. Very frustrating.
    See #903 (comment)

  4. AviVahl commented on Mar 10, 2026

    @AviVahl
    AviVahl
    on Mar 10, 2026

    This was also reported in #921

  5. quirogas
    added
    type: processA process-related concern. May include testing, release, or the like.
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    and removed
    priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Mar 12, 2026
  6. quirogas
    self-assigned this
    on Mar 12, 2026
  7. quirogas
    linked a pull request that will close this issuechore: release main #931on Mar 15, 2026
  8. quirogas
    closed this as completedin #931on Mar 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p1Important issue which blocks shipping the next release. Will be fixed prior to next release.type: processA process-related concern. May include testing, release, or the like.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions