Skip to content

Update cloudinary to 2.9.0+ to drop deprecated q transitive dependency #141

Closed

Description

@ooloth

Why

cloudinary@2.8.0 transitively depends on the q promise library, which its own maintainer marks as deprecated and replaced by native Promises; cloudinary@2.9.0 removed this dependency. Upgrading eliminates a deprecated package from the production dependency tree.

Current state

package.json specifies cloudinary: "^2.8.0" and package-lock.json locks it at 2.8.0. This version declares q as a production dependency (no "dev": true in the lockfile entry). The q package's own package.json description reads: "You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises." cloudinary@2.9.0 and later do not depend on q.

Ideal state

  • package-lock.json pins cloudinary at 2.9.0 or later.
  • Running npm ls q finds no q package in the resolved tree.
  • All Cloudinary image transforms on the site continue to resolve correctly after the upgrade.

Starting points

  • package.json — the cloudinary version constraint (^2.8.0)
  • package-lock.json — to verify q is absent after updating

QA plan

  1. Run npm update cloudinary — expect package-lock.json to update cloudinary to 2.10.0 (the current latest within ^2.8.0).
  2. Run npm ls q — expect no output (no q in the resolved tree).
  3. Run npm run build — expect a clean build with no type or compilation errors.
  4. Open a page that renders a Cloudinary image — expect the image to load at the correct transformed URL.

Done when

cloudinary is at 2.9.0 or later in package-lock.json and q does not appear anywhere in the production dependency tree.

Activity

  1. ooloth commented on Oct 18, 2026

    @ooloth
    OwnerAuthor

    Since 2d73fa4, io/cloudinary/client.ts sets hide_sensitive: true to keep api_key:api_secret out of SDK errors. When upgrading, confirm the new version still honours that option. describeCloudinaryFailure remains as a fallback either way.

  2. ooloth commented on Nov 7, 2026

    @ooloth
    OwnerAuthor

    Finished by #219, which updated cloudinary to 2.11.0. package-lock.json at 18633bc locks cloudinary 2.11.0 and has no q entry, and the production home page serves Cloudinary image URLs after the deploy. 2.11.0 still honours hide_sensitive: true: lib/api_client/execute_request.js deletes auth and the Authorization header from the request options it reports when the option is set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions