Feature request: official Dart server-side SDK
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- api, backend-api-design
Research direction
No implementation files or tests are identified in the issue. Start by reviewing the existing Node.js SDK and the Cloudinary REST API surface, then define the Dart package scope, supported helpers, and maintenance expectations. Done would mean an officially supported Dart package is implemented, published on pub.dev, and validated against the agreed API scope.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
We run a production backend on server-side Dart (Firebase Cloud Functions, Dart AOT runtime) alongside our Flutter app. Today the only way to call the Cloudinary API from Dart is a hand-rolled HTTP client over the REST API — no typed models, no maintained auth/retry/pagination helpers, and drift whenever the API changes.
Describe the solution you'd like
An official (or officially-supported) Dart package published on pub.dev, equivalent in scope to your Node.js SDK. Dart is now a first-class server language (AOT Cloud Functions, Cloud Run, Dart Frog, Serverpod), and the Flutter ecosystem makes one language across mobile + backend valuable.
Alternatives considered
- Hand-written REST client over
package:http(current approach — high maintenance). - Keeping these integrations in a separate Node.js service purely because no Dart SDK exists.
Additional context
Our team maintains both a Flutter app and a Dart backend; a Dart SDK would let us consolidate. Happy to help test and give feedback.
- Dominant language
- JavaScript
- Stars
- 672
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudinary/cloudinary_npm
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
cloudinary/cloudinary_npm#746 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
cloudinary/cloudinary_npm#734 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
cloudinary/cloudinary_npm#713 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
cloudinary/cloudinary_npm#712 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
cloudinary/cloudinary_npm#702 · 2 comments ·
All issues in cloudinary/cloudinary_npm
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
discovery:other factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vercel/ai#25068 · 4 comments ·
Maintainers usually reply within 1 day
-
needs-triage typo
Difficulty 1/5 Under an hour Newbie friendliness 88/100
llm-d-incubation/llm-d-scaling-manager#122 ·
Maintainers usually reply within 1 day
-
create-strapi-app doesn't await writing license.txt, so a failed write skips its error handlingOpenflag: invalid template issue: bug severity: low source: cli status: pending reproduction version: 5
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
strapi/strapi#28637 · 1 comment ·
Maintainers usually reply within 2 days