Files

T

Paul Rastoin fdab89ae02 Move twenty-client-sdk to dev dep (#21611 )

# Introduction
The `twenty-client-sdk` is always provided and injected at runtime by
the twenty-server instance
Which mean that even if in your app locally you're using
twenty-client-sdk `1.0` installing this app on twenty instance `2.0`
will result in injecting another `twenty-client-sdk`

That's the expected behavior and tradeof

The twenty-app devdep should only be used to guide local devxp following
typesafety and so on

A user can still locally generated its own twenty-client-sdk and publish
it if necessary

<!-- This is an auto-generated description by cubic. -->
<a
href="https://cubic.dev/pr/twentyhq/twenty/pull/21611?utm_source=github"
target="_blank" rel="noopener noreferrer"
data-no-image-dialog="true"><picture><source
media="(prefers-color-scheme: dark)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source
media="(prefers-color-scheme: light)"
srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img
alt="Review in cubic"
src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a>
<!-- End of auto-generated description by cubic. -->

2026-06-15 14:46:22 +00:00

1.9 KiB

Raw Blame History

Changelog

All notable changes to the Twenty SDK are documented in this file.

The format follows Keep a Changelog, and this package adheres to Semantic Versioning.

[Unreleased]

Changed

twenty-client-sdk should now be a dev dependency too. Although app code imports it (CoreApiClient, MetadataApiClient, RestApiClient), Twenty provides it at runtime — logic functions get it from a generated SDK layer and front components resolve it from server-served modules — so the installed copy is only needed for typechecking and the deploy-time build. Newly scaffolded apps now place it under devDependencies. Moving it is recommended (not required: the server already strips it from the deployed runtime), and keeps the installed app leaner:
```
  "dependencies": {
-   "twenty-client-sdk": "^2.13.0"
  },
  "devDependencies": {
+   "twenty-client-sdk": "^2.13.0"
  }
```
twenty build now also emits a warning when twenty-client-sdk is still listed under dependencies.

[2.8.0]

Breaking Changes

twenty-sdk must now be a dev dependency. It ships the twenty CLI and the build/scaffolding tooling, which only run at development and build time — it is never imported by a published app's runtime. Newly scaffolded apps already place it under devDependencies. Apps created before 2.8.0 must move it when upgrading:
```
  "dependencies": {
    "twenty-client-sdk": "^2.8.0"
-   "twenty-sdk": "^2.8.0"
  },
  "devDependencies": {
+   "twenty-sdk": "^2.8.0"
  }
```
Then reinstall with rm -rf node_modules && yarn install. twenty-client-sdk stays under dependencies because app code imports it at runtime.

twenty build now emits a warning when twenty-sdk is still listed under dependencies, so existing apps are flagged automatically.

1.9 KiB Raw Blame History

Changelog

[Unreleased]

Changed

[2.8.0]

Breaking Changes

1.9 KiB

Raw Blame History