Elgato_dark/twenty
1
0
Fork 0
mirror of https://github.com/twentyhq/twenty synced 2026-04-21 13:37:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 17
twenty/package.json

222 lines
7.2 KiB
JSON
Raw Normal View History

Migrate to a monorepo structure (#2909)
2023-12-10 17:10:54 +00:00
{
[ENHC] Create `Yarn` constraints to validate `node` version (#10542) ## Introduction This is PR is a suggestion ! And should be discussed With yarn `^4`, during installation won't raise an error if current dev env does not satisfies the `engines` policy. We have usually 10+ contributors support request regarding higher node version issue per week I would have preferred a very declarative integration using npm [engines](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#engines) but this does not seems to be natively supported by `yarn` We should keep in mind that this might block any machines from our CICD if they have diff node version installed ( such as running the project on a different node version could result in bugs too ) ## Implem Created a yarn [constraints](https://yarnpkg.com/features/constraints) run after each installation that checking if current node version satisfies defined engines range ( might also be done for others engines entries ) I assume we will always have the same engines policy for every packages, at least that's not a consideration from now ## Further We could refactor our package.json engines into only one using `Yarn.set` etc ## Resource - https://yarnpkg.com/configuration/yarnrc - https://yarnpkg.com/features/constraints ## Note - Not running constraints in `preInstall` hook as won't be effective on fresh install - [engine-strict](https://docs.npmjs.com/cli/v8/using-npm/config#engine-strict) is an npm-config - [devEngines](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines) are npm feature too ( for instance pnpm current PR https://github.com/pnpm/pnpm/issues/8153 ) ## Conclusion As always any suggestions are more than welcomed !
2025-02-27 14:18:07 +00:00
"private": true,
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"dependencies": {
Upgrade Apollo Client to v4 and refactor error handling (#18584) ## Summary This PR upgrades Apollo Client from v3.10.0 to v4 and refactors error handling patterns across the codebase to use a new centralized `useSnackBarOnQueryError` hook. ## Key Changes - **Dependency Update**: Upgraded `@apollo/client` from `^3.10.0` to `^3.11.0` in root package.json - **New Hook**: Added `useSnackBarOnQueryError` hook for centralized Apollo query error handling with snack bar notifications - **Error Handling Refactor**: Updated 100+ files to use the new error handling pattern: - Removed direct `ApolloError` imports where no longer needed - Replaced manual error handling logic with `useSnackBarOnQueryError` hook - Simplified error handling in hooks and components across multiple modules - **GraphQL Codegen**: Updated codegen configuration files to work with Apollo Client v3.11.0 - **Type Definitions**: Added TypeScript declaration file for `apollo-upload-client` module - **Test Updates**: Updated test files to reflect new error handling patterns ## Notable Implementation Details - The new `useSnackBarOnQueryError` hook provides a consistent way to handle Apollo query errors with automatic snack bar notifications - Changes span across multiple feature areas: auth, object records, settings, workflows, billing, and more - All changes maintain backward compatibility while improving code maintainability and reducing duplication - Jest configuration updated to work with the new Apollo Client version https://claude.ai/code/session_019WGZ6Rd7sEHuBg9sTrXRqJ --------- Co-authored-by: Claude <noreply@anthropic.com>
2026-03-13 13:59:46 +00:00
"@apollo/client": "^4.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@floating-ui/react": "^0.24.3",
Added Linaria for performance optimization (#5693) - Added Linaria to have compiled CSS on our optimized field displays - Refactored mocks for performance stories on fields - Refactored generateRecordChipData into a global context, computed only when we fetch object metadata items. - Refactored ChipFieldDisplay - Refactored PhoneFieldDisplay
2024-06-12 14:31:07 +00:00
"@linaria/core": "^6.2.0",
"@linaria/react": "^6.2.1",
Complete color refactoring (#15414) # Complete color refactoring Closes https://github.com/twentyhq/core-team-issues/issues/1779 - Updated all colors to use Radix colors with P3 color space allowing for brighter colors - Created our own gray scale interpolated on Radix's scale to have the same values for grays as the old ones in the app - Introduced dark and light colors as well as there transparent versions - Added many new colors from radix that can be used in the tags or in the graphs - Updated multiple color utilities to match new behaviors - Changed the computation of Avatar colors to return only colors from the theme (before it was random hsl) These changes allow the user to use new colors in tags or charts, the colors are brighter and with better contrast. We have a full range of color variations from 1 to 12 where before we only had 4 adaptative colors. All these changes will allow us to develop custom themes for the user soon, where users can choose their accent colors, background colors and there contrast.
2025-10-29 18:08:51 +00:00
"@radix-ui/colors": "^3.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@sniptt/guards": "^0.2.0",
496 add open in full page button on command menu record page (#10659) Closes https://github.com/twentyhq/core-team-issues/issues/496 I upgraded react tabler icons to the latest version to be able to use the newest icons. The option menu was no longer accessible on right drawer record pages, this pr fixes this and creates a new button which opens the record show page. This button is accessible via the shortcut `Command` + `Enter` https://github.com/user-attachments/assets/570071b2-4406-40bd-be48-a0e5e430ed70
2025-03-05 11:02:31 +00:00
"@tabler/icons-react": "^3.31.0",
Complete linaria migration (#18361) ## Summary Completes the migration of the frontend styling system from **Emotion** (`@emotion/styled`, `@emotion/react`) to **Linaria** (`@linaria/react`, `@linaria/core`), a zero-runtime CSS-in-JS library where styles are extracted at build time. This is the final step of the migration — all ~494 files across `twenty-front`, `twenty-ui`, `twenty-website`, and `twenty-sdk` are now fully converted. ## Changes ### Styling Migration (across ~480 component files) - Replaced all `@emotion/styled` imports with `@linaria/react` - Converted runtime theme access patterns (`({ theme }) => theme.x.y`) to build-time `themeCssVariables` CSS custom properties - Replaced `useTheme()` hook (from Emotion) with `useContext(ThemeContext)` where runtime theme values are still needed (e.g., passing colors to non-CSS props like icon components) - Removed `@emotion/react` `css` helper usages in favor of Linaria template literals ### Dependency & Configuration Changes - **Removed**: `@emotion/react`, `@emotion/styled` from root `package.json` - **Added**: `@wyw-in-js/babel-preset`, `next-with-linaria` (for twenty-website SSR support) - Updated Nx generator defaults from `@emotion/styled` to `@linaria/react` in `nx.json` - Simplified `vite.config.ts` (removed Emotion-specific configuration) - Updated `twenty-website/next.config.js` to use `next-with-linaria` for SSR Linaria support ### Storybook & Testing - Removed `ThemeProvider` from Emotion in Storybook previews (`twenty-front`, `twenty-sdk`) - Now relies solely on `ThemeContextProvider` for theme injection ### Documentation - Removed the temporary `docs/emotion-to-linaria-migration-plan.md` (migration complete) - Updated `CLAUDE.md` and `README.md` to reflect Linaria as the styling stack - Updated frontend style guide docs across all locales ## How it works Linaria extracts styles at build time via the `@wyw-in-js/vite` plugin. All expressions in `styled` template literals must be **statically evaluable** — no runtime theme objects or closures over component state. - **Static styles** use `themeCssVariables` which map to CSS custom properties (`var(--theme-color-x)`) - **Runtime theme access** (for non-CSS use cases like icon `color` props) uses `useContext(ThemeContext)` instead of Emotion's `useTheme()`
2026-03-03 23:50:06 +00:00
"@wyw-in-js/babel-preset": "^1.0.6",
Remove preconstruct, update wyw (#13844) To simplify our setup, moving back to Vite to build twenty-shared. Also upgrading wyw --------- Co-authored-by: prastoin <paul@twenty.com>
2025-08-12 10:43:35 +00:00
"@wyw-in-js/vite": "^0.7.0",
6181 workflows create a custom code executor (#6235) Closes #6181 ## Testing - download Altair graphql dev tool https://altairgraphql.dev/#download - create a file locally `test.ts` containing: ``` export const handler = async (event: object, context: object) => { return { test: 'toto', data: event['data'] }; } ``` - play those requests in Altair: mutation UpsertFunction($file: Upload!) { upsertFunction(name: "toto", file: $file) } mutation ExecFunction { executeFunction(name:"toto", payload: {data: "titi"}) } - it will run the local driver, add those env variable to test with lambda driver ``` CUSTOM_CODE_ENGINE_DRIVER_TYPE=lambda LAMBDA_REGION=eu-west-2 LAMBDA_ROLE=<ASK_ME> ```
2024-07-17 15:53:01 +00:00
"archiver": "^7.0.1",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"danger-plugin-todos": "^1.3.1",
"date-fns": "^2.30.0",
feat: add Display calendar settings (#4164) * feat: add Color calendar setting Closes #4067 * fix: fix wrong imports * feat: add Display calendar settings Closes #4068 * feat: add 12h/24h in Format option labels * fix tests * Fix * Fix --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-24 11:50:32 +00:00
"date-fns-tz": "^2.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"deep-equal": "^2.2.2",
"file-type": "16.5.4",
feat: record group chevron button (#9645) This ticket is related to this Discord post https://discord.com/channels/1130383047699738754/1328756649657110559
2025-01-16 09:03:05 +00:00
"framer-motion": "^11.18.0",
Changed the auto matching of columns in import (#12181) This PR changes the way we do automatching in the import feature. It uses [Fuse.js](https://www.fusejs.io/) to do a fuzzy text search on fields and sub-fields. The labels of sub-fields are now derived from the common config constant we have for sub-fields.
2025-05-23 16:33:18 +00:00
"fuse.js": "^7.1.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"googleapis": "105",
"hex-rgb": "^5.0.0",
Add immer in package.json (#13635)
2025-08-05 12:34:20 +00:00
"immer": "^10.1.1",
Start Jotai Migration (#17893) ## Recoil → Jotai progressive migration: infrastructure + ChipFieldDisplay ### Benchmark In the beginning, there was no hope: <img width="1180" height="948" alt="image" src="https://github.com/user-attachments/assets/f8635991-52e6-4958-8240-6ba7214132b2" /> Then the hope was reborn <img width="2070" height="948" alt="image" src="https://github.com/user-attachments/assets/be1182b9-1c8d-4fdc-ab4c-1484ad74449d" /> ### Approach We introduce a **V2 state management layer** backed by Jotai that mirrors the existing Recoil API, enabling component-by-component migration without a big-bang rewrite. #### V2 API (Jotai-backed, Recoil-ergonomic) - `createStateV2` / `createFamilyStateV2` — drop-in replacements for `createState` / `createFamilyState`, returning wrapper types over Jotai atoms - `useRecoilValueV2`, `useRecoilStateV2`, `useFamilyRecoilValueV2`, etc. — thin wrappers around Jotai's `useAtomValue` / `useAtom` / `useSetAtom` - A shared `jotaiStore` (via `createStore()`) passed to a `<JotaiProvider>` wrapping `<RecoilRoot>`, also accessible imperatively for dual-writes #### Dual-write bridge for progressive migration For state shared between migrated and non-migrated components, we use **dual-write**: writers update both the Recoil atom and the Jotai V2 atom (via `jotaiStore.set()`). This avoids sync components or extra subscriptions. Write sites updated: `useUpsertRecordsInStore`, `useSetRecordTableData`, `ListenRecordUpdatesEffect`, `RecordShowEffect`, `useLoadRecordIndexStates`, `useUpdateObjectViewOptions`. #### First migration: ChipFieldDisplay render path - `useChipFieldDisplay` → reads `recordStoreFamilyStateV2` via `useFamilyRecoilValueV2` (was `useRecoilValue(recordStoreFamilyState)`) - `RecordChip` → reads `recordIndexOpenRecordInStateV2` via `useRecoilValueV2` (was `useRecoilValue(recordIndexOpenRecordInState)`) - `Avatar` (twenty-ui) and event handlers (`useOpenRecordInCommandMenu`) left on Recoil — not on the render path / in a different package #### Pattern for migrating additional state 1. Create V2 atom: `createStateV2` or `createFamilyStateV2` 2. Add `jotaiStore.set(v2Atom, value)` at each write site 3. Switch readers to `useRecoilValueV2(v2Atom)` 4. Once all readers are migrated, remove the Recoil atom and dual-writes #### Why not jotai-recoil-adapter? Evaluated [jotai-recoil-adapter](https://github.com/clockelliptic/jotai-recoil-adapter) — not production-ready (21 open issues, no React 19, forces providerless mode, missing types). We built a purpose-built thin layer instead.
2026-02-12 15:05:38 +00:00
"jotai": "^2.17.1",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"libphonenumber-js": "^1.10.26",
"lodash.camelcase": "^4.3.0",
5901 refactor email and calendar auto contact creation to create them by batch (#6038) Closes #5901
2024-06-27 14:37:34 +00:00
"lodash.chunk": "^4.2.0",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"lodash.compact": "^3.0.1",
Fix frontend bug when filtering with special character (#9307) Fixes #8767
2025-01-02 12:43:27 +00:00
"lodash.escaperegexp": "^4.1.2",
Refactor Views by cleaning the code, relying on apolloCache and improving performances (#4516) * Wip refactoring view * Post merge conflicts * Fix review * Add create view capability * Fix create object missing view * Fix tests
2024-03-20 13:21:58 +00:00
"lodash.groupby": "^4.6.0",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"lodash.identity": "^3.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"lodash.isempty": "^4.4.0",
"lodash.isequal": "^4.5.0",
"lodash.isobject": "^3.0.2",
"lodash.kebabcase": "^4.1.1",
feat: add Month headers to Show Page Calendar tab (#4326) Closes #4288
2024-03-08 09:22:23 +00:00
"lodash.mapvalues": "^4.6.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"lodash.merge": "^4.6.2",
POC: generate twenty-server package.json with Nx (#3654) * POC: generate twenty-server package.json with Nx * Re-add passport * Fix instal --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 21:16:21 +00:00
"lodash.omit": "^4.5.0",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"lodash.pickby": "^4.6.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"lodash.snakecase": "^4.1.1",
"lodash.upperfirst": "^4.3.1",
"microdiff": "^1.3.2",
Complete linaria migration (#18361) ## Summary Completes the migration of the frontend styling system from **Emotion** (`@emotion/styled`, `@emotion/react`) to **Linaria** (`@linaria/react`, `@linaria/core`), a zero-runtime CSS-in-JS library where styles are extracted at build time. This is the final step of the migration — all ~494 files across `twenty-front`, `twenty-ui`, `twenty-website`, and `twenty-sdk` are now fully converted. ## Changes ### Styling Migration (across ~480 component files) - Replaced all `@emotion/styled` imports with `@linaria/react` - Converted runtime theme access patterns (`({ theme }) => theme.x.y`) to build-time `themeCssVariables` CSS custom properties - Replaced `useTheme()` hook (from Emotion) with `useContext(ThemeContext)` where runtime theme values are still needed (e.g., passing colors to non-CSS props like icon components) - Removed `@emotion/react` `css` helper usages in favor of Linaria template literals ### Dependency & Configuration Changes - **Removed**: `@emotion/react`, `@emotion/styled` from root `package.json` - **Added**: `@wyw-in-js/babel-preset`, `next-with-linaria` (for twenty-website SSR support) - Updated Nx generator defaults from `@emotion/styled` to `@linaria/react` in `nx.json` - Simplified `vite.config.ts` (removed Emotion-specific configuration) - Updated `twenty-website/next.config.js` to use `next-with-linaria` for SSR Linaria support ### Storybook & Testing - Removed `ThemeProvider` from Emotion in Storybook previews (`twenty-front`, `twenty-sdk`) - Now relies solely on `ThemeContextProvider` for theme injection ### Documentation - Removed the temporary `docs/emotion-to-linaria-migration-plan.md` (migration complete) - Updated `CLAUDE.md` and `README.md` to reflect Linaria as the styling stack - Updated frontend style guide docs across all locales ## How it works Linaria extracts styles at build time via the `@wyw-in-js/vite` plugin. All expressions in `styled` template literals must be **statically evaluable** — no runtime theme objects or closures over component state. - **Static styles** use `themeCssVariables` which map to CSS custom properties (`var(--theme-color-x)`) - **Runtime theme access** (for non-CSS use cases like icon `color` props) uses `useContext(ThemeContext)` instead of Emotion's `useTheme()`
2026-03-03 23:50:06 +00:00
"next-with-linaria": "^1.3.0",
POC: generate twenty-server package.json with Nx (#3654) * POC: generate twenty-server package.json with Nx * Re-add passport * Fix instal --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 21:16:21 +00:00
"planer": "^1.2.0",
Introduce remote table entity (#4994) We will require remote table entity to map distant table name and local foreign table name. Introducing the entity: - new source of truth to know if a table is sync or not - created synchronously at the same time as metadata and foreign table Adding a few more changes: - exception rather than errors so the user can see these - `pluralize` library that will allow to stop adding `Remote` suffix on names --------- Co-authored-by: Thomas Trompette <thomast@twenty.com>
2024-04-17 08:52:10 +00:00
"pluralize": "^8.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"react": "^18.2.0",
"react-dom": "^18.2.0",
"react-responsive": "^9.0.2",
feat: upgrade nx to latest (#18404) Upgraded NX to resolve some dependabot alerts caused by transitive dependencies, but after the upgrade, it appears those transitive dependency issues were not fixed by NX in the first place. Creating this PR with the upgrade regardless to avoid wasted work. Used `npx nx@latest migrate latest` from the documentation to automate the upgrade and it bumped all the dependencies changed in `package.json` for compatibility - `react-router-dom` and `swc` ones too. Ran tests, ran builds, started the development server and used the application - everything looks good after the upgrade.
2026-03-05 08:36:33 +00:00
"react-router-dom": "^6.30.3",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"react-tooltip": "^5.13.1",
fix: next-mdx-remote related dependabot alerts (#18244) Resolves [Dependabot Alert 485](https://github.com/twentyhq/twenty/security/dependabot/485) and [Dependabot Alert 486](https://github.com/twentyhq/twenty/security/dependabot/486). Bumped up `next-mdx-remote` to v6.0.0 and `remark-gfm` to v4.0.1 for compatibility - no breaking changes for our use-case.
2026-02-25 22:12:23 +00:00
"remark-gfm": "^4.0.1",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"rxjs": "^7.2.0",
"semver": "^7.5.4",
Fix Storybook Configuration for Windows Development Environment (#7904) #### Description This PR resolves issue #7903 regarding the Storybook configuration for Windows development environments. Previously, the configuration script generated forward slashes instead of backslashes, leading to errors when running the command `npx nx run twenty-front:storybook:serve:dev --configuration=modules` on Windows systems. #### Changes Made - Updated the Storybook configuration to ensure that backslashes are used in file paths for Windows environments, preventing command execution errors. #### How to Test 1. **Run Storybook Command**: - On a Windows machine, execute the command: ``` npx nx run twenty-front:storybook:serve:dev --configuration=modules ``` - Ensure that the command runs successfully without any path-related errors. 2. **Verify Configuration**: - Check the Storybook configuration files to confirm that paths are using backslashes where applicable. - Test the same command on non-Windows environments to verify that there are no regressions. #### Related Issue - Fixes #7903
2024-10-21 16:28:31 +00:00
"slash": "^5.1.0",
Refactored Date to Temporal in critical date zones (#16544) Fixes https://github.com/twentyhq/twenty/issues/16110 This PR implements Temporal to replace the legacy Date object, in all features that are time zone sensitive. (around 80% of the app) Here we define a few utils to handle Temporal primitives and obtain an easier DX for timezone manipulation, front end and back end. This PR deactivates the usage of timezone from the graph configuration, because for now it's always UTC and is not really relevant, let's handle that later. Workflows code and backend only code that don't take user input are using UTC time zone, the affected utils have not been refactored yet because this PR is big enough. # New way of filtering on date intervals As we'll progressively rollup Temporal everywhere in the codebase and remove `Date` JS object everywhere possible, we'll use the way to filter that is recommended by Temporal. This way of filtering on date intervals involves half-open intervals, and is the preferred way to avoid edge-cases with DST and smallest time increment edge-case. ## Filtering endOfX with DST edge-cases Some day-light save time shifts involve having no existing hour, or even day on certain days, for example Samoa Islands have no 30th of December 2011 : https://www.timeanddate.com/news/time/samoa-dateline.html, it jumps from 29th to 31st, so filtering on `< next period start` makes it easier to let the date library handle the strict inferior comparison, than filtering on `≤ end of period` and trying to compute manually the end of the period. For example for Samoa Islands, is end of day `2011-12-29T23:59:59.999` or is it `2011-12-30T23:59:59.999` ? If you say I don't need to know and compute it, because I want everything strictly before `2011-12-29T00:00:00 + start of next day (according to the library which knows those edge-cases)`, then you have a 100% deterministic way of computing date intervals in any timezone, for any day of any year. Of course the Samoa example is an extreme one, but more common ones involve DST shifts of 1 hour, which are still problematic on certain days of the year. ## Computing the exact _end of period_ Having an open interval filtering, with `[included - included]` instead of half-open `[included - excluded)`, forces to compute the open end of an interval, which often involves taking an arbitrary unit like minute, second, microsecond or nanosecond, which will lead to edge-case of unhandled values. For example, let's say my code computes endOfDay by setting the time to `23:59:59.999`, if another library, API, or anything else, ends up giving me a date-time with another time precision `23:59:59.999999999` (down to the nanosecond), then this date-time will be filtered out, while it should not. The good deterministic way to avoid 100% of those complex bugs is to create a half-open filter : `≥ start of period` to `< start of next period` For example : `≥ 2025-01-01T00:00:00` to `< 2025-01-02T00:00:00` instead of `≥ 2025-01-01T00:00:00` to `≤ 2025-01-01T23:59:59.999` Because, `2025-01-01T00:00:00` = `2025-01-01T00:00:00.000` = `2025-01-01T00:00:00.000000` = `2025-01-01T00:00:00.000000000` => no risk of error in computing start of period But `2025-01-01T23:59:59` ≠ `2025-01-01T23:59:59.999` ≠ `2025-01-01T23:59:59.999999` ≠ `2025-01-01T23:59:59.999999999` => existing risk of error in computing end of period This is why an half-open interval has no risk of error in computing a date-time interval filter. Here is a link to this debate : https://github.com/tc39/proposal-temporal/issues/2568 > For this reason, we recommend not calculating the exact nanosecond at the end of the day if it's not absolutely necessary. For example, if it's needed for <= comparisons, we recommend just changing the comparison code. So instead of <= zdtEndOfDay your code could be < zdtStartOfNextDay which is easier to calculate and not subject to the issue of not knowing which unit is the right one. > > [Justin Grant](https://github.com/justingrant), top contributor of Temporal ## Application to our codebase Applying this half-open filtering paradigm to our codebase means we would have to rename `IS_AFTER` to `IS_AFTER_OR_EQUAL` and to keep `IS_BEFORE` (or even `IS_STRICTLY_BEFORE`) to make this half-open interval self-explanatory everywhere in the codebase, this will avoid any confusion. See the relevant issue : https://github.com/twentyhq/core-team-issues/issues/2010 In the mean time, we'll keep this operand and add this semantic in the naming everywhere possible. ## Example with a different user timezone Example on a graph grouped by week in timezone Pacific/Samoa, on a computer running on Europe/Paris : <img width="342" height="511" alt="image" src="https://github.com/user-attachments/assets/9e7d5121-ecc4-4233-835b-f59293fbd8c8" /> Then the associated data in the table view, with our **half-open date-time filter** : <img width="804" height="262" alt="image" src="https://github.com/user-attachments/assets/28efe1d7-d2fc-4aec-b521-bada7f980447" /> And the associated SQL query result to see how DATE_TRUNC in Postgres applies its internal start of week logic : <img width="709" height="220" alt="image" src="https://github.com/user-attachments/assets/4d0542e1-eaae-4b4b-afa9-5005f48ffdca" /> The associated SQL query without parameters to test in your SQL client : ```SQL SELECT "opportunity"."closeDate" as "close_date", TO_CHAR(DATE_TRUNC('week', "opportunity"."closeDate", 'Pacific/Samoa') AT TIME ZONE 'Pacific/Samoa', 'YYYY-MM-DD') AS "DATE_TRUNC by week start in timezone Pacific/Samoa", "opportunity"."name" FROM "workspace_1wgvd1injqtife6y4rvfbu3h5"."opportunity" "opportunity" ORDER BY "opportunity"."closeDate" ASC NULLS LAST ``` # Date picker simplification (not in this PR) Our DatePicker component, which is wrapping `react-datepicker` library component, is now exposing plain dates as string instead of Date object. The Date object is still used internally to manage the library component, but since the date picker calendar is only manipulating plain dates, there is no need to add timezone management to it, and no need to expose a handleChange with Date object. The timezone management relies on date time inputs now. The modification has been made in a previous PR : https://github.com/twentyhq/twenty/issues/15377 but it's good to reference it here. # Calendar feature refactor Calendar feature has been refactored to rely on Temporal.PlainDate as much as possible, while leaving some date-fns utils to avoid re-coding them. Since the trick is to use utils to convert back and from Date object in exec env reliably, we can do it everywhere we need to interface legacy Date object utils and Temporal related code. ## TimeZone is now shown on Calendar : <img width="894" height="958" alt="image" src="https://github.com/user-attachments/assets/231f8107-fad6-4786-b532-456692c20f1d" /> ## Month picker has been refactored <img width="503" height="266" alt="image" src="https://github.com/user-attachments/assets/cb90bc34-6c4d-436d-93bc-4b6fb00de7f5" /> Since the days weren't useful, the picker has been refactored to remove the days. # Miscellaneous - Fixed a bug with drag and drop edge-case with 2 items in a list. # Improvements ## Lots of chained operations It would be nice to create small utils to avoid repeated chained operations, but that is how Temporal is designed, a very small set of primitive operations that allow to compose everything needed. Maybe we'll have wrappers on top of Temporal in the coming years. ## Creation of Temporal objects is throwing errors If the input is badly formatted Temporal will throw, we might want to adopt a global strategy to avoid that. Example : ```ts const newPlainDate = Temporal.PlainDate.from('bad-string'); // Will throw ```
2025-12-23 17:40:26 +00:00
"temporal-polyfill": "^0.3.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"ts-key-enum": "^2.0.12",
Run yarn dedupe and upgrade TS (#13853) Upgrading TS to the latest version, and cleaning up packages with yarn dedupe
2025-08-12 13:18:59 +00:00
"tslib": "^2.8.1",
POC: generate twenty-server package.json with Nx (#3654) * POC: generate twenty-server package.json with Nx * Re-add passport * Fix instal --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 21:16:21 +00:00
"type-fest": "4.10.1",
Run yarn dedupe and upgrade TS (#13853) Upgrading TS to the latest version, and cleaning up packages with yarn dedupe
2025-08-12 13:18:59 +00:00
"typescript": "5.9.2",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"uuid": "^9.0.0",
"vite-tsconfig-paths": "^4.2.1",
"xlsx-ugnis": "^0.19.3",
Migrate from Zod v3 to v4 (#14639) Closes [#1526](https://github.com/twentyhq/core-team-issues/issues/1526) --------- Co-authored-by: Félix Malfait <felix@twenty.com> Co-authored-by: Félix Malfait <felix.malfait@gmail.com>
2025-09-24 16:29:05 +00:00
"zod": "^4.1.11"
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
},
"devDependencies": {
chore: set up twenty-emails config so build isn't needed in development (#3619) * chore: set up twenty-emails config so build isn't needed in development * fix: fix script dependency * chore: use @vitejs/plugin-react-swc * Remove useless dependancy * Fix typing * chore: use baseUrl in twenty-emails * chore: fix docker server prod build * refactor: optimize Docker file and tsconfig * fix: fix WORKDIR in docker --------- Co-authored-by: martmull <martmull@hotmail.fr>
2024-01-29 09:17:12 +00:00
"@babel/core": "^7.14.5",
"@babel/preset-react": "^7.14.5",
Added Linaria for performance optimization (#5693) - Added Linaria to have compiled CSS on our optimized field displays - Refactored mocks for performance stories on fields - Refactored generateRecordChipData into a global context, computed only when we fetch object metadata items. - Refactored ChipFieldDisplay - Refactored PhoneFieldDisplay
2024-06-12 14:31:07 +00:00
"@babel/preset-typescript": "^7.24.6",
feat: upgrade to Storybook version 10 (#17110) Upgraded to Storybook 10. We still use `@storybook/test-runner` for testing since it appears it'd require more work to move from Jest to Vitest than I initially anticipated, but I completed this PR to fix `storybook:serve:dev` - it takes time to load, but it works the way it used to with Storybook 8. https://github.com/user-attachments/assets/7afc32c6-4bcf-4b37-b83b-8d00d28dda15
2026-01-13 08:18:07 +00:00
"@chromatic-com/storybook": "^4.1.3",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@graphql-codegen/cli": "^3.3.1",
"@graphql-codegen/client-preset": "^4.1.0",
"@graphql-codegen/typescript": "^3.0.4",
"@graphql-codegen/typescript-operations": "^3.0.4",
"@graphql-codegen/typescript-react-apollo": "^3.3.7",
feat: upgrade nx to latest (#18404) Upgraded NX to resolve some dependabot alerts caused by transitive dependencies, but after the upgrade, it appears those transitive dependency issues were not fixed by NX in the first place. Creating this PR with the upgrade regardless to avoid wasted work. Used `npx nx@latest migrate latest` from the documentation to automate the upgrade and it bumped all the dependencies changed in `package.json` for compatibility - `react-router-dom` and `swc` ones too. Ran tests, ran builds, started the development server and used the application - everything looks good after the upgrade.
2026-03-05 08:36:33 +00:00
"@nx/jest": "22.5.4",
"@nx/js": "22.5.4",
"@nx/react": "22.5.4",
"@nx/storybook": "22.5.4",
"@nx/vite": "22.5.4",
"@nx/web": "22.5.4",
Migrate from ESLint to OxLint (#18443) ## Summary Fully replaces ESLint with OxLint across the entire monorepo: - **Replaced all ESLint configs** (`eslint.config.mjs`) with OxLint configs (`.oxlintrc.json`) for every package: `twenty-front`, `twenty-server`, `twenty-emails`, `twenty-ui`, `twenty-shared`, `twenty-sdk`, `twenty-zapier`, `twenty-docs`, `twenty-website`, `twenty-apps/*`, `create-twenty-app` - **Migrated custom lint rules** from ESLint plugin format to OxLint JS plugin system (`@oxlint/plugins`), including `styled-components-prefixed-with-styled`, `no-hardcoded-colors`, `sort-css-properties-alphabetically`, `graphql-resolvers-should-be-guarded`, `rest-api-methods-should-be-guarded`, `max-consts-per-file`, and Jotai-related rules - **Migrated custom rule tests** from ESLint `RuleTester` + Jest to `oxlint/plugins-dev` `RuleTester` + Vitest - **Removed all ESLint dependencies** from `package.json` files and regenerated lockfiles - **Updated Nx targets** (`lint`, `lint:diff-with-main`, `fmt`) in `nx.json` and per-project `project.json` to use `oxlint` commands with proper `dependsOn` for plugin builds - **Updated CI workflows** (`.github/workflows/ci-*.yaml`) — no more ESLint executor - **Updated IDE setup**: replaced `dbaeumer.vscode-eslint` with `oxc.oxc-vscode` extension, configured `source.fixAll.oxc` and format-on-save with Prettier - **Replaced all `eslint-disable` comments** with `oxlint-disable` equivalents across the codebase - **Updated docs** (`twenty-docs`) to reference OxLint instead of ESLint - **Renamed** `twenty-eslint-rules` package to `twenty-oxlint-rules` ### Temporarily disabled rules (tracked in `OXLINT_MIGRATION_TODO.md`) | Rule | Package | Violations | Auto-fixable | |------|---------|-----------|-------------| | `twenty/sort-css-properties-alphabetically` | twenty-front | 578 | Yes | | `typescript/consistent-type-imports` | twenty-server | 3814 | Yes | | `twenty/max-consts-per-file` | twenty-server | 94 | No | ### Dropped plugins (no OxLint equivalent) `eslint-plugin-project-structure`, `lingui/*`, `@stylistic/*`, `import/order`, `prefer-arrow/prefer-arrow-functions`, `eslint-plugin-mdx`, `@next/eslint-plugin-next`, `eslint-plugin-storybook`, `eslint-plugin-react-refresh`. Partial coverage for `jsx-a11y` and `unused-imports`. ### Additional fixes (pre-existing issues exposed by merge) - Fixed `EmailThreadPreview.tsx` broken import from main rename (`useOpenEmailThreadInSidePanel`) - Restored truthiness guard in `getActivityTargetObjectRecords.ts` - Fixed `AgentTurnResolver` return types to match entity (virtual `fileMediaType`/`fileUrl` are resolved via `@ResolveField()`) ## Test plan - [x] `npx nx lint twenty-front` passes - [x] `npx nx lint twenty-server` passes - [x] `npx nx lint twenty-docs` passes - [x] Custom oxlint rules validated with Vitest: `npx nx test twenty-oxlint-rules` - [x] `npx nx typecheck twenty-front` passes - [x] `npx nx typecheck twenty-server` passes - [x] CI workflows trigger correctly with `dependsOn: ["twenty-oxlint-rules:build"]` - [x] IDE linting works with `oxc.oxc-vscode` extension
2026-03-06 00:03:50 +00:00
"@oxlint/plugins": "^1.51.0",
Begin refactoring AI module (#12464) Cleaning up to prepare for a few tests
2025-06-05 10:28:42 +00:00
"@sentry/types": "^8",
feat: upgrade to Storybook version 10 (#17110) Upgraded to Storybook 10. We still use `@storybook/test-runner` for testing since it appears it'd require more work to move from Jest to Vitest than I initially anticipated, but I completed this PR to fix `storybook:serve:dev` - it takes time to load, but it works the way it used to with Storybook 8. https://github.com/user-attachments/assets/7afc32c6-4bcf-4b37-b83b-8d00d28dda15
2026-01-13 08:18:07 +00:00
"@storybook-community/storybook-addon-cookie": "^5.0.0",
"@storybook/addon-coverage": "^3.0.0",
fix: upgrade storybook to latest to resolve dependabot alert (#18285) Resolves [Dependabot Alert 509](https://github.com/twentyhq/twenty/security/dependabot/509). Upgraded storybook and related packages to latest, also fixed a failing test to match what the DOM really contains.
2026-02-27 09:58:54 +00:00
"@storybook/addon-docs": "^10.2.13",
"@storybook/addon-links": "^10.2.13",
"@storybook/addon-vitest": "^10.2.13",
feat: upgrade to Storybook version 10 (#17110) Upgraded to Storybook 10. We still use `@storybook/test-runner` for testing since it appears it'd require more work to move from Jest to Vitest than I initially anticipated, but I completed this PR to fix `storybook:serve:dev` - it takes time to load, but it works the way it used to with Storybook 8. https://github.com/user-attachments/assets/7afc32c6-4bcf-4b37-b83b-8d00d28dda15
2026-01-13 08:18:07 +00:00
"@storybook/icons": "^2.0.1",
fix: upgrade storybook to latest to resolve dependabot alert (#18285) Resolves [Dependabot Alert 509](https://github.com/twentyhq/twenty/security/dependabot/509). Upgraded storybook and related packages to latest, also fixed a failing test to match what the DOM really contains.
2026-02-27 09:58:54 +00:00
"@storybook/react-vite": "^10.2.13",
feat: upgrade to Storybook version 10 (#17110) Upgraded to Storybook 10. We still use `@storybook/test-runner` for testing since it appears it'd require more work to move from Jest to Vitest than I initially anticipated, but I completed this PR to fix `storybook:serve:dev` - it takes time to load, but it works the way it used to with Storybook 8. https://github.com/user-attachments/assets/7afc32c6-4bcf-4b37-b83b-8d00d28dda15
2026-01-13 08:18:07 +00:00
"@storybook/test-runner": "^0.24.2",
feat: upgrade nx to latest (#18404) Upgraded NX to resolve some dependabot alerts caused by transitive dependencies, but after the upgrade, it appears those transitive dependency issues were not fixed by NX in the first place. Creating this PR with the upgrade regardless to avoid wasted work. Used `npx nx@latest migrate latest` from the documentation to automate the upgrade and it bumped all the dependencies changed in `package.json` for compatibility - `react-router-dom` and `swc` ones too. Ran tests, ran builds, started the development server and used the application - everything looks good after the upgrade.
2026-03-05 08:36:33 +00:00
"@swc-node/register": "^1.11.1",
"@swc/cli": "^0.7.10",
"@swc/core": "^1.15.11",
"@swc/helpers": "~0.5.19",
chore: scope package.json deps to packages (#13835) - Move dev-only types to devDependencies - Move frontend-only deps from root to twenty-front - Add website-only deps to twenty-website - Fix react-phone-number-input patch path CI should validate.
2025-08-12 05:15:20 +00:00
"@swc/jest": "^0.2.39",
feat: upgrade Storybook to version 9 (#17077) Upgraded from 8.6.15 to 9.1.17 in two steps: - 8.6.15 -> 9.0.0 - 9.0.0 -> 9.1.17 I had to disable `storybook-addon-cookie` since it is not supported for Storybook 9. However, I do intend to upgrade to Storybook 10 when this is merged, so we can replace the aforementioned add-on with this fork specifically created to support Storybook 10 and above: https://www.npmjs.com/package/@storybook-community/storybook-addon-cookie. Additionally, once we upgrade to Version 10 successfully, I will start looking into integrating the official Vitest add-on.
2026-01-11 13:54:41 +00:00
"@testing-library/dom": "^10.4.0",
Upgrade to Node22 (#12488) BlocknoteJS requires an ESM module where our server is CJS, this forced us to pin the server-util version, which led us to force the resolution of several packages, leading to bugs downstream. From Node 22.12 Node supports requiring ESM modules (available from Node 22.0 with a flag). So I upgrade the module. I picked Node 22 and not Node 23 or Node 24 because 22 is the LTS and we don't plan to change node versions frequently. If you remain on Node 18, things should still mostly work, except if you edit a Rich Text field. I also starting changing the default runtime for Serverless Functions which isn't directly related. This means new serverless functions will be created on Node 22, but we will still need another PR to migrate existing serverless functions before September (end of support by AWS). (In this PR I also remove the upgrade commands from 0.43 since they rely on Blocknote and I didn't want to have to deal with this) --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
2025-06-06 16:35:30 +00:00
"@testing-library/jest-dom": "^6.6.3",
"@testing-library/react": "^16.3.0",
feat: fetch and parse full gmail message (#5160) first part of https://github.com/twentyhq/twenty/issues/4108 related PR https://github.com/twentyhq/twenty/pull/5081 --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-05-20 15:29:35 +00:00
"@types/addressparser": "^1.0.3",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/bcrypt": "^5.0.0",
"@types/bytes": "^3.1.1",
chore: add nx/project.json to twenty-chrome-extension (#5217) Fix for `build` CI on `twenty-chrome-extension` --------- Co-authored-by: Thaïs Guigon <guigon.thais@gmail.com>
2024-05-06 09:33:48 +00:00
"@types/chrome": "^0.0.267",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/deep-equal": "^1.0.1",
First Application POC (#14382) Quick proof of concept for twenty-apps + twenty-cli, with local development / hot reload Let's discuss it! https://github.com/user-attachments/assets/c6789936-cd5f-4110-a265-863a6ac1af2d
2025-09-10 13:12:38 +00:00
"@types/fs-extra": "^11.0.4",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/graphql-fields": "^1.3.6",
First Application POC (#14382) Quick proof of concept for twenty-apps + twenty-cli, with local development / hot reload Let's discuss it! https://github.com/user-attachments/assets/c6789936-cd5f-4110-a265-863a6ac1af2d
2025-09-10 13:12:38 +00:00
"@types/inquirer": "^9.0.9",
Upgrade SWC Core and Storybook to v8 (#13799) This is is a blocker for various sub-migrations
2025-08-11 10:02:33 +00:00
"@types/jest": "^30.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/lodash.camelcase": "^4.3.7",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"@types/lodash.compact": "^3.0.9",
Fix frontend bug when filtering with special character (#9307) Fixes #8767
2025-01-02 12:43:27 +00:00
"@types/lodash.escaperegexp": "^4.1.9",
feat: multi-workspace (frontend) (#4232) * select workspace component * generateJWT mutation * workspaces state and hooks * requested changes * mutation fix * requested changes * user workpsace delete call * migration to drop and createt user workspace * revert select props * add DropdownMenu * seperate multi-workspace dropdown as component * Signup button displayed accurately * update seed data for multi-workspace * lint fix * lint fix * css fix * lint fix * state fix * isDefined check * refactor * add default workspace constants for logo and name * update migration * lint fix * isInviteMode check on sign-in/up * removeWorkspaceMember mutation * import fixes * prop name fix * backfill migration * handle edge cases * refactor * remove migration query * delete user on no-workspace found condition * emit workspaceMember.deleted * Fix event class and unrelated fix linked to a previously missing dependency * Edit migration (I did it in prod manually) * Revert changes * Fix tests * Fix conflicts --------- Co-authored-by: Félix Malfait <felix.malfait@gmail.com>
2024-03-20 13:43:41 +00:00
"@types/lodash.groupby": "^4.6.9",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"@types/lodash.identity": "^3.0.9",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/lodash.isempty": "^4.4.7",
"@types/lodash.isequal": "^4.5.7",
"@types/lodash.isobject": "^3.0.7",
"@types/lodash.kebabcase": "^4.1.7",
feat: add Month headers to Show Page Calendar tab (#4326) Closes #4288
2024-03-08 09:22:23 +00:00
"@types/lodash.mapvalues": "^4.6.9",
Fix missing lodash type dependency breaking front container build
2024-03-25 15:26:28 +00:00
"@types/lodash.omit": "^4.5.9",
fix: fix storybook:build memory allocation error in CI (#5284)
2024-05-03 17:19:21 +00:00
"@types/lodash.pickby": "^4.6.9",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/lodash.snakecase": "^4.1.7",
"@types/lodash.upperfirst": "^4.3.7",
"@types/ms": "^0.7.31",
Upgrade to Node 24 (#13730) As described in title
2025-08-07 15:02:12 +00:00
"@types/node": "^24.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/passport-google-oauth20": "^2.0.11",
"@types/passport-jwt": "^3.0.8",
Remove hoisting on server (#13821) Testing a different approach to fix broken buildPackageJson on server build How i have tested: A. Local contributor setup - run yarn - build server - run yarn workspace focus - run server on dist B. self-host - docker build Note: I think the dependencies I have added are suboptimized as the image went from 2GB to 3.5GB. We might need to be more accurate
2025-08-11 13:58:05 +00:00
"@types/passport-microsoft": "^2.1.0",
Date filter improvements (#5917) (#7196) Solves issue #5917. This PR is now ready for the first review! Filters do not fully work yet, there's a problem applying multiple filters like the following: ``` { and: [ { [correspondingField.name]: { gte: start.toISOString(), } as DateFilter, }, { [correspondingField.name]: { lte: end.toISOString(), } as DateFilter, }, ], } ``` I'll do my best to dig into it tonight! --------- Co-authored-by: Félix Malfait <felix@twenty.com>
2024-09-27 13:57:38 +00:00
"@types/pluralize": "^0.0.33",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/react": "^18.2.39",
Date picker for Date and DateTime field input (#4981) - Implemented correct mask for Date and DateTime field in InternalDatePicker - Use only keyDown event and click outside in InternalDatePicker and DateInput - Refactored InternalDatePicker UI to have month and year displayed - Fixed bug and synchronized date value between the different inputs that can change it --------- Co-authored-by: gitstart-twenty <gitstart-twenty@users.noreply.github.com> Co-authored-by: v1b3m <vibenjamin6@gmail.com> Co-authored-by: Matheus <matheus_benini@hotmail.com>
2024-04-16 14:58:08 +00:00
"@types/react-datepicker": "^6.2.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"@types/react-dom": "^18.2.15",
"@types/supertest": "^2.0.11",
"@types/uuid": "^9.0.2",
feat: add TypeScript Go (tsgo) for faster type checking (#17211) ## Summary - Add `@typescript/native-preview` (tsgo) for dramatically faster type checking on frontend projects - Configure tsgo as default for frontend projects (twenty-front, twenty-ui, twenty-shared, etc.) - Keep tsc for twenty-server (faster for NestJS decorator-heavy code) - Fix type imports for tsgo compatibility (DOMPurify, AxiosInstance) - Remove deprecated `baseUrl` from tsconfigs where safe ## Performance Results | Project | tsgo | tsc -b | Speedup | |---------|------|--------|---------| | **twenty-front** | 1.4s | 60.7s | **43x faster** | | **twenty-server** | 2m42s | 1m10s | tsc is faster (decorators) | tsgo excels at modern React/JSX codebases but struggles with decorator-heavy NestJS backends, so we use the optimal checker for each. ## Usage ```bash # Default (tsgo for frontend, tsc for backend) nx typecheck twenty-front nx typecheck twenty-server # Force tsc fallback if needed nx typecheck twenty-front --configuration=tsc # Force tsgo on backend (slower, not recommended) nx typecheck twenty-server --configuration=tsgo ``` ## Test plan - [x] `nx typecheck twenty-front` passes with tsgo - [x] `nx typecheck twenty-server` passes with tsc - [x] `nx run-many -t typecheck --exclude=fireflies` passes - [ ] CI tests pass
2026-01-19 11:46:34 +00:00
"@typescript/native-preview": "^7.0.0-dev.20260116.1",
chore: upgrade @swc/core to 1.15.11 and align SWC ecosystem (#18088) ## Summary - Upgrades `@swc/core` from 1.13.3 to **1.15.11** (swc_core v56), which introduces CBOR-based plugin serialization replacing rkyv, eliminating strict version-matching between SWC core and Wasm plugins - Upgrades `@lingui/swc-plugin` from ^5.6.0 to **^5.11.0** (swc_core 50.2.3, built with `--cfg=swc_ast_unknown` for cross-version compatibility) - Upgrades `@swc/plugin-emotion` from 10.0.4 to **14.6.0** (swc_core 53, also with backward-compat feature) - Upgrades companion packages: `@swc-node/register` 1.8.0 → 1.11.1, `@swc/helpers` ~0.5.2 → ~0.5.18, `@vitejs/plugin-react-swc` 3.11.0 → 4.2.3 ### Why this is safe now Starting from `@swc/core v1.15.0`, SWC replaced the rkyv serialization scheme with CBOR (a self-describing format) and added `Unknown` AST enum variants. Plugins built with `swc_core >= 47` and `--cfg=swc_ast_unknown` are now forward-compatible across `@swc/core` versions. Both `@lingui/swc-plugin@5.10.1+` and `@swc/plugin-emotion@14.0.0+` have this support, meaning the old version-matching nightmare between Lingui and SWC is largely solved. Reference: https://github.com/lingui/swc-plugin/issues/179 ## Test plan - [x] `yarn install` resolves without errors - [x] `npx nx build twenty-shared` succeeds - [x] `npx nx build twenty-ui` succeeds (validates @swc/plugin-emotion@14.6.0) - [x] `npx nx typecheck twenty-front` succeeds - [x] `npx nx build twenty-front` succeeds (validates vite + swc + lingui pipeline) - [x] `npx nx build twenty-emails` succeeds (validates lingui plugin) - [x] Frontend jest tests pass (validates @swc/jest + @lingui/swc-plugin) - [x] Server jest tests pass (validates server-side SWC + lingui) Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-19 15:27:56 +00:00
"@vitejs/plugin-react-swc": "4.2.3",
Bump @vitest/browser-playwright from 4.0.17 to 4.0.18 (#17884) Bumps [@vitest/browser-playwright](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser-playwright) from 4.0.17 to 4.0.18. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vitest-dev/vitest/releases"><code>@​vitest/browser-playwright</code>'s releases</a>.</em></p> <blockquote> <h2>v4.0.18</h2> <h3>   🚀 Experimental Features</h3> <ul> <li><strong>experimental</strong>: Add <code>onModuleRunner</code> hook to <code>worker.init</code>  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9286">vitest-dev/vitest#9286</a> <a href="https://github.com/vitest-dev/vitest/commit/ea837de7d"><!-- raw HTML omitted -->(ea837)<!-- raw HTML omitted --></a></li> </ul> <h3>   🐞 Bug Fixes</h3> <ul> <li>Use <code>meta.url</code> in <code>createRequire</code>  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9441">vitest-dev/vitest#9441</a> <a href="https://github.com/vitest-dev/vitest/commit/e057281ca"><!-- raw HTML omitted -->(e0572)<!-- raw HTML omitted --></a></li> <li><strong>browser</strong>: Hide injected data-testid attributes  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9503">vitest-dev/vitest#9503</a> <a href="https://github.com/vitest-dev/vitest/commit/f89899cd8"><!-- raw HTML omitted -->(f8989)<!-- raw HTML omitted --></a></li> <li><strong>ui</strong>: Process artifact attachments when generating HTML reporter  -  by <a href="https://github.com/macarie"><code>@​macarie</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9472">vitest-dev/vitest#9472</a> <a href="https://github.com/vitest-dev/vitest/commit/225435647"><!-- raw HTML omitted -->(22543)<!-- raw HTML omitted --></a></li> </ul> <h5>    <a href="https://github.com/vitest-dev/vitest/compare/v4.0.17...v4.0.18">View changes on GitHub</a></h5> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vitest-dev/vitest/commit/4d3e3c61b9b237447699deab9aca0eb9d6039978"><code>4d3e3c6</code></a> chore: release v4.0.18</li> <li>See full diff in <a href="https://github.com/vitest-dev/vitest/commits/v4.0.18/packages/browser-playwright">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@vitest/browser-playwright&package-manager=npm_and_yarn&previous-version=4.0.17&new-version=4.0.18)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Abdullah. <125115953+mabdullahabaid@users.noreply.github.com>
2026-02-12 13:35:22 +00:00
"@vitest/browser-playwright": "^4.0.18",
"@vitest/coverage-istanbul": "^4.0.18",
"@vitest/coverage-v8": "^4.0.18",
[ENHC] Create `Yarn` constraints to validate `node` version (#10542) ## Introduction This is PR is a suggestion ! And should be discussed With yarn `^4`, during installation won't raise an error if current dev env does not satisfies the `engines` policy. We have usually 10+ contributors support request regarding higher node version issue per week I would have preferred a very declarative integration using npm [engines](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#engines) but this does not seems to be natively supported by `yarn` We should keep in mind that this might block any machines from our CICD if they have diff node version installed ( such as running the project on a different node version could result in bugs too ) ## Implem Created a yarn [constraints](https://yarnpkg.com/features/constraints) run after each installation that checking if current node version satisfies defined engines range ( might also be done for others engines entries ) I assume we will always have the same engines policy for every packages, at least that's not a consideration from now ## Further We could refactor our package.json engines into only one using `Yarn.set` etc ## Resource - https://yarnpkg.com/configuration/yarnrc - https://yarnpkg.com/features/constraints ## Note - Not running constraints in `preInstall` hook as won't be effective on fresh install - [engine-strict](https://docs.npmjs.com/cli/v8/using-npm/config#engine-strict) is an npm-config - [devEngines](https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines) are npm feature too ( for instance pnpm current PR https://github.com/pnpm/pnpm/issues/8153 ) ## Conclusion As always any suggestions are more than welcomed !
2025-02-27 14:18:07 +00:00
"@yarnpkg/types": "^4.0.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"chromatic": "^6.18.0",
Added Single Command for Frontend + Backend (#3909) * Added single command * Fix according to review --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 11:23:29 +00:00
"concurrently": "^8.2.2",
fix: prototype pollution vulnerability in parse-git-config (#15242) Fixes [Dependabot Alert 203](https://github.com/twentyhq/twenty/security/dependabot/203) - prototype pollution vulnerability in parse-git-config. parse-git-config was a dependency for danger@11.3.1, but danger@13.0.4 does not depend on it.
2025-10-22 09:42:24 +00:00
"danger": "^13.0.4",
chore(workflows): update permissions across GitHub Actions workflows … (#14919) …for consistency
2025-10-06 15:36:41 +00:00
"dotenv-cli": "^7.4.4",
esBuild serverless (#14886) Use [esbuild](https://esbuild.github.io/) to Build serverless entire folder instead of just the src/index.ts file. Application serverless folders can contain code organized in folders ## Small example This now works: <img width="1330" height="686" alt="image" src="https://github.com/user-attachments/assets/e0639517-492d-4b64-8722-18bbe94dacb0" />
2025-10-06 08:47:42 +00:00
"esbuild": "^0.25.10",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"http-server": "^14.1.1",
"jest": "29.7.0",
Upgrade to Node22 (#12488) BlocknoteJS requires an ESM module where our server is CJS, this forced us to pin the server-util version, which led us to force the resolution of several packages, leading to bugs downstream. From Node 22.12 Node supports requiring ESM modules (available from Node 22.0 with a flag). So I upgrade the module. I picked Node 22 and not Node 23 or Node 24 because 22 is the LTS and we don't plan to change node versions frequently. If you remain on Node 18, things should still mostly work, except if you edit a Rich Text field. I also starting changing the default runtime for Serverless Functions which isn't directly related. This means new serverless functions will be created on Node 22, but we will still need another PR to migrate existing serverless functions before September (end of support by AWS). (In this PR I also remove the upgrade commands from 0.43 since they rely on Blocknote and I didn't want to have to deal with this) --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
2025-06-06 16:35:30 +00:00
"jest-environment-jsdom": "30.0.0-beta.3",
Setup the foundation for Twenty UI library. (#4423) * feat: create a separate package for twenty-ui, extract the pill component with hard-coded theme values into it, and use the component inside twenty-front to complete the setup * feat: extract the light and the dark theme into twenty-ui and update the AppThemeProvider component inside twenty-front to consume themes from twenty-ui * fix: create a decorator inside preview.tsx to provide a default theme to storybook development server * fix: remove redundant type declarations and revert back the naming convention for theme declarations * fix: introduce a default value for pill label within the story for development server * fix: introduce the nx script into package.json for twenty-ui and resolve imports for theme type within the package * fix: remove the pill component from the twenty-front package along with the story for it * fix: revert the package versions to those before running the nx cli command for storybook init * feat: update readme to include details for building the ui library and starting the storybook development server * fix: include details about twenty-ui inside jest.config for twenty-front to complete front-jest job * - Added preview head for font - Added theme addon for light/dark switch - Added ComponentDecorator --------- Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
2024-03-13 13:21:18 +00:00
"jest-environment-node": "^29.4.1",
TWNTY-3381 - Add tests for `modules/apollo` (#3530) Add tests for `modules/apollo` Co-authored-by: gitstart-twenty <gitstart-twenty@users.noreply.github.com> Co-authored-by: v1b3m <vibenjamin6@gmail.com>
2024-01-18 10:25:27 +00:00
"jest-fetch-mock": "^3.0.3",
chore: set up twenty-emails config so build isn't needed in development (#3619) * chore: set up twenty-emails config so build isn't needed in development * fix: fix script dependency * chore: use @vitejs/plugin-react-swc * Remove useless dependancy * Fix typing * chore: use baseUrl in twenty-emails * chore: fix docker server prod build * refactor: optimize Docker file and tsconfig * fix: fix WORKDIR in docker --------- Co-authored-by: martmull <martmull@hotmail.fr>
2024-01-29 09:17:12 +00:00
"jsdom": "~22.1.0",
Replace test-runner with vitest for storybook (#17187)
2026-01-18 03:25:45 +00:00
"msw": "^2.12.7",
"msw-storybook-addon": "^2.0.6",
feat: upgrade nx to latest (#18404) Upgraded NX to resolve some dependabot alerts caused by transitive dependencies, but after the upgrade, it appears those transitive dependency issues were not fixed by NX in the first place. Creating this PR with the upgrade regardless to avoid wasted work. Used `npx nx@latest migrate latest` from the documentation to automate the upgrade and it bumped all the dependencies changed in `package.json` for compatibility - `react-router-dom` and `swc` ones too. Ran tests, ran builds, started the development server and used the application - everything looks good after the upgrade.
2026-03-05 08:36:33 +00:00
"nx": "22.5.4",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"prettier": "^3.1.1",
"raw-loader": "^4.0.2",
"rimraf": "^5.0.5",
"source-map-support": "^0.5.20",
fix: upgrade storybook to latest to resolve dependabot alert (#18285) Resolves [Dependabot Alert 509](https://github.com/twentyhq/twenty/security/dependabot/509). Upgraded storybook and related packages to latest, also fixed a failing test to match what the DOM really contains.
2026-02-27 09:58:54 +00:00
"storybook": "^10.2.13",
feat: upgrade to Storybook version 10 (#17110) Upgraded to Storybook 10. We still use `@storybook/test-runner` for testing since it appears it'd require more work to move from Jest to Vitest than I initially anticipated, but I completed this PR to fix `storybook:serve:dev` - it takes time to load, but it works the way it used to with Storybook 8. https://github.com/user-attachments/assets/7afc32c6-4bcf-4b37-b83b-8d00d28dda15
2026-01-13 08:18:07 +00:00
"storybook-addon-mock-date": "2.0.0",
fix: upgrade storybook to latest to resolve dependabot alert (#18285) Resolves [Dependabot Alert 509](https://github.com/twentyhq/twenty/security/dependabot/509). Upgraded storybook and related packages to latest, also fixed a failing test to match what the DOM really contains.
2026-02-27 09:58:54 +00:00
"storybook-addon-pseudo-states": "^10.2.13",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"supertest": "^6.1.3",
"ts-jest": "^29.1.1",
"ts-loader": "^9.2.3",
"ts-node": "10.9.1",
Speed up twenty-emails build by replacing vite-plugin-dts with tsgo (#17857) ## Summary - Removed `vite-plugin-dts` (which used `tsc` internally) from the Vite build and replaced DTS generation with `tsgo` as a sequential post-build step — **~0.7s vs 1-10s**. - Disabled `reportCompressedSize` to skip gzip computation for 64 output files. - Converted the build target to an explicit `nx:run-commands` executor with sequential `vite build` → `tsgo` commands. The `twenty-emails:build` step goes from ~22s to ~7s under load. ## Test plan - [x] `nx build twenty-emails` produces both JS (64 files) and DTS (74 files) correctly - [x] `dist/index.d.ts` exports match the source `src/index.ts` - [x] Full `nx build twenty-server` succeeds end-to-end - [ ] CI build passes Made with [Cursor](https://cursor.com) --------- Co-authored-by: Cursor <cursoragent@cursor.com>
2026-02-13 10:39:26 +00:00
"tsc-alias": "^1.8.16",
chore: make twenty-server nest command scripts depend on twenty-email… (#4055) chore: make twenty-server nest command scripts depend on twenty-emails build Closes #4013
2024-02-20 13:35:09 +00:00
"tsconfig-paths": "^4.2.0",
Fix frontend tests (#6585) Fix a few broken tests
2024-08-09 06:38:01 +00:00
"tsx": "^4.17.0",
Create twenty app e2e test ci (#18497) # Introduction Verifies whole following flow: - Create and sdk app build and publication - Global create-twenty-app installation - Creating an app - installing app dependencies - auth:login - app:build - function:execute - Running successfully auto-generated integration tests ## Create twenty app options refactor Allow having a flow that do not require any prompt
2026-03-11 15:30:28 +00:00
"verdaccio": "^6.3.1",
Replace test-runner with vitest for storybook (#17187)
2026-01-18 03:25:45 +00:00
"vite": "^7.0.0",
Bump @vitest/browser-playwright from 4.0.17 to 4.0.18 (#17884) Bumps [@vitest/browser-playwright](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser-playwright) from 4.0.17 to 4.0.18. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/vitest-dev/vitest/releases"><code>@​vitest/browser-playwright</code>'s releases</a>.</em></p> <blockquote> <h2>v4.0.18</h2> <h3>   🚀 Experimental Features</h3> <ul> <li><strong>experimental</strong>: Add <code>onModuleRunner</code> hook to <code>worker.init</code>  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9286">vitest-dev/vitest#9286</a> <a href="https://github.com/vitest-dev/vitest/commit/ea837de7d"><!-- raw HTML omitted -->(ea837)<!-- raw HTML omitted --></a></li> </ul> <h3>   🐞 Bug Fixes</h3> <ul> <li>Use <code>meta.url</code> in <code>createRequire</code>  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9441">vitest-dev/vitest#9441</a> <a href="https://github.com/vitest-dev/vitest/commit/e057281ca"><!-- raw HTML omitted -->(e0572)<!-- raw HTML omitted --></a></li> <li><strong>browser</strong>: Hide injected data-testid attributes  -  by <a href="https://github.com/sheremet-va"><code>@​sheremet-va</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9503">vitest-dev/vitest#9503</a> <a href="https://github.com/vitest-dev/vitest/commit/f89899cd8"><!-- raw HTML omitted -->(f8989)<!-- raw HTML omitted --></a></li> <li><strong>ui</strong>: Process artifact attachments when generating HTML reporter  -  by <a href="https://github.com/macarie"><code>@​macarie</code></a> in <a href="https://redirect.github.com/vitest-dev/vitest/issues/9472">vitest-dev/vitest#9472</a> <a href="https://github.com/vitest-dev/vitest/commit/225435647"><!-- raw HTML omitted -->(22543)<!-- raw HTML omitted --></a></li> </ul> <h5>    <a href="https://github.com/vitest-dev/vitest/compare/v4.0.17...v4.0.18">View changes on GitHub</a></h5> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/vitest-dev/vitest/commit/4d3e3c61b9b237447699deab9aca0eb9d6039978"><code>4d3e3c6</code></a> chore: release v4.0.18</li> <li>See full diff in <a href="https://github.com/vitest-dev/vitest/commits/v4.0.18/packages/browser-playwright">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@vitest/browser-playwright&package-manager=npm_and_yarn&previous-version=4.0.17&new-version=4.0.18)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Abdullah. <125115953+mabdullahabaid@users.noreply.github.com>
2026-02-12 13:35:22 +00:00
"vitest": "^4.0.18"
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
},
Update scripts and documentation to use nx and new monorepo architecture (#2912) * Update scripts and documentation to use nx and new monorepo architecture * Start fixing docker * Migrate eslint plugin and postgres setup * Fix docker * Fix patches * Fix * fix: wip try to fix the patches * Apply patches --------- Co-authored-by: Jérémy Magrin <jeremy.magrin@gmail.com>
2023-12-11 09:54:57 +00:00
"engines": {
Expect node `24.5.0` (#13734) Unless I'm mistaken the project does not run with node `24.0.0` Switching to node `24.5.0` ( as defined in vscode node runtime requirements in https://github.com/twentyhq/twenty/pull/13730 ) seems to fix the issue ```ts Successfully compiled: 2897 files with swc (188.32ms) (node:77006) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated. (Use `node --trace-deprecation ...` to show where the warning was created) Watching for file changes. /Users/paulrastoin/ws/twenty/node_modules/buffer-equal-constant-time/index.js:37 var origSlowBufEqual = SlowBuffer.prototype.equal; ^ TypeError: Cannot read properties of undefined (reading 'prototype') ``` Updating engines so local constraint suggest a functional node version
2025-08-07 16:22:28 +00:00
"node": "^24.5.0",
Update scripts and documentation to use nx and new monorepo architecture (#2912) * Update scripts and documentation to use nx and new monorepo architecture * Start fixing docker * Migrate eslint plugin and postgres setup * Fix docker * Fix patches * Fix * fix: wip try to fix the patches * Apply patches --------- Co-authored-by: Jérémy Magrin <jeremy.magrin@gmail.com>
2023-12-11 09:54:57 +00:00
"npm": "please-use-yarn",
"yarn": ">=4.0.2"
},
Migrate to a monorepo structure (#2909)
2023-12-10 17:10:54 +00:00
"license": "AGPL-3.0",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"name": "twenty",
Update yarn and remove explicit hardened mode (#13092) Updates yarn to the latest version 4.9.2 (from 4.4.0). Also removes the explicit `enableHardenedMode` from yarnrc as it significantly slows down installation. This is already enabled automatically for pull requests on Github, thus preventing lockfile poisoning where it's relevant. See <https://yarnpkg.com/features/security#hardened-mode>: > in most cases you won't even have to think about it - the hardened mode is enabled by default when Yarn detects it runs in a pull request from a public GitHub repository. It can additionally be enabled explicitly for specific CI jobs by using an environment variable, if desired: > The hardened mode can be set (or disabled) [...] by defining `YARN_ENABLE_HARDENED_MODE=1|0` in your environment variables If this is the case, yarn still recommends **not** enabling it everywhere: > **DANGER** > > The hardened mode makes installs significantly slower as Yarn has to query the registry to make sure the information contained in the lockfile are accurate. If your CI pipeline runs multiple jobs, we recommend disabling the hardened mode in all but one of them so as to limit the performance impact. --------- Co-authored-by: prastoin <paul@twenty.com>
2025-07-08 12:57:08 +00:00
"packageManager": "yarn@4.9.2",
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
"resolutions": {
fix: graphql uncontrolled resource consumption vulnerability (#15260) Fixes [Dependabot Alert 73](https://github.com/twentyhq/twenty/security/dependabot/73) - graphql uncontrolled resource consumption vulnerability. Updated the patch version - from 16.8.0 to 16.8.1 - and this patch only touches the issue identified by the alert. <p align="center"> <img width="1175" height="472" alt="image" src="https://github.com/user-attachments/assets/4f809f03-1e63-4412-822c-227712d1e395" /> </p> Manually tested a few mutations, ran test cases, and everything seems to work fine. Not expecting it to break anything. Two files changed in the original patch fix: https://github.com/graphql/graphql-js/commit/8f4c64eb6a7112a929ffeef00caa67529b3f2fcf
2025-10-22 14:07:47 +00:00
"graphql": "16.8.1",
chore: setup twenty-ui absolute path alias (#4732) Split from https://github.com/twentyhq/twenty/pull/4518 - Setup `@ui/*` as an internal alias to reference `twenty-ui/src`. - Configures twenty-front to understand the `@ui/*` alias on development mode, so twenty-ui can be hot reloaded. - When building on production mode, twenty-front needs twenty-ui to be built beforehand (which is automatic with the `dependsOn` option). - Configures twenty-front to understand the `@ui/*` alias when launching tests, so there is no need to re-build twenty-ui for tests. --------- Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
2024-04-04 13:38:01 +00:00
"type-fest": "4.10.1",
Run yarn dedupe and upgrade TS (#13853) Upgrading TS to the latest version, and cleaning up packages with yarn dedupe
2025-08-12 13:18:59 +00:00
"typescript": "5.9.2",
Upgrade to Node22 (#12488) BlocknoteJS requires an ESM module where our server is CJS, this forced us to pin the server-util version, which led us to force the resolution of several packages, leading to bugs downstream. From Node 22.12 Node supports requiring ESM modules (available from Node 22.0 with a flag). So I upgrade the module. I picked Node 22 and not Node 23 or Node 24 because 22 is the LTS and we don't plan to change node versions frequently. If you remain on Node 18, things should still mostly work, except if you edit a Rich Text field. I also starting changing the default runtime for Serverless Functions which isn't directly related. This means new serverless functions will be created on Node 22, but we will still need another PR to migrate existing serverless functions before September (end of support by AWS). (In this PR I also remove the upgrade commands from 0.43 since they rely on Blocknote and I didn't want to have to deal with this) --------- Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
2025-06-06 16:35:30 +00:00
"graphql-redis-subscriptions/ioredis": "^5.6.0",
Move tools/eslint-rules to packages/twenty-eslint-rules (#17203) ## Summary Moves the custom ESLint rules from `tools/eslint-rules` to `packages/twenty-eslint-rules` for better organization within the monorepo packages structure. ## Changes - Move `eslint-rules` from `tools/` to `packages/twenty-eslint-rules` - Use `loadWorkspaceRules` from `@nx/eslint-plugin` to load custom rules - Update all ESLint configs to use the `twenty/` rule prefix instead of `@nx/workspace-` - Update `project.json`, `jest.config.mjs` with new paths - Update `package.json` workspaces and `nx.json` cache inputs - Update Dockerfile reference ## Technical Details The custom ESLint rules are now loaded using Nx's `loadWorkspaceRules` utility which: - Handles TypeScript transpilation automatically - Allows loading workspace rules from any directory - Provides a cleaner approach than the previous `@nx/workspace-` convention ## Testing - Verified all 17 custom ESLint rules load correctly from the new location - Verified linting works on dependent packages (twenty-front, twenty-server, etc.)
2026-01-17 06:37:17 +00:00
"@lingui/core": "5.1.2",
chore(twenty-front): migrate command-menu, workflow, page-layout and UI modules from Emotion to Linaria (PR 4-6/10) (#18342) ## Summary Continues the Emotion → Linaria migration (PR 4-6 from the [migration plan](docs/emotion-to-linaria-migration-plan.md)). Migrates **311 files** across four module groups: | Module | Files | |---|---| | command-menu | 53 | | workflow | 84 | | page-layout | 84 | | UI (partial - first ~80 files) | ~80 | | twenty-ui (TEXT_INPUT_STYLE) | 1 | | misc (hooks, keyboard-shortcut-menu, file-upload) | ~9 | ### Migration patterns applied - `import styled from '@emotion/styled'` → `import { styled } from '@linaria/react'` - `import { useTheme } from '@emotion/react'` → `import { useContext } from 'react'` + `import { ThemeContext } from 'twenty-ui/theme'` - `${({ theme }) => theme.X.Y.Z}` → `${themeCssVariables.X.Y.Z}` (static CSS variables) - `theme.spacing(N)` → `themeCssVariables.spacing[N]` - `styled(motion.div)` → `motion.create(StyledBase)` (11 components) - `styled(Component)<TypeParams>` → wrapper div approach for non-HTML elements - Multi-declaration interpolations split into one CSS property per interpolation - Interpolation return types fixed (`&&` → ternary `? : ''`) - `TEXT_INPUT_STYLE` converted from function to static string constant (backward compatible) - Emotion `<Global>` replaced with `useEffect` style injection - Complex runtime-dependent styles use CSS custom properties via `style={}` prop ### After this PR - **Remaining files**: ~400 (object-record: ~160, settings: ~200, UI: ~44) - **No breaking changes**: CSS variables resolve identically to the previous Emotion theme values
2026-03-03 15:42:03 +00:00
"@types/qs": "6.9.16",
"@wyw-in-js/transform@npm:0.6.0": "patch:@wyw-in-js/transform@npm%3A0.7.0#~/.yarn/patches/@wyw-in-js-transform-npm-0.7.0-ba641dc99f.patch",
"@wyw-in-js/transform@npm:0.7.0": "patch:@wyw-in-js/transform@npm%3A0.7.0#~/.yarn/patches/@wyw-in-js-transform-npm-0.7.0-ba641dc99f.patch"
Embrace nx monorepo structure with root package.json (#3255) * Upgrade to node 18.17.1 and regroup dependencies in root package.json * Sort package.json * Fix lint * Migrate zapier
2024-01-05 13:59:58 +00:00
},
"version": "0.2.1",
fix: fix root start script (#5032) Fixes #5022 See https://nx.dev/recipes/running-tasks/root-level-scripts#setup
2024-04-19 16:28:02 +00:00
"nx": {},
Added Single Command for Frontend + Backend (#3909) * Added single command * Fix according to review --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 11:23:29 +00:00
"scripts": {
docs: localize navigation tabs and groups for supported locales (#15811)
2025-11-14 21:03:54 +00:00
"docs:generate": "tsx packages/twenty-docs/scripts/generate-docs-json.ts",
"docs:generate-navigation-template": "tsx packages/twenty-docs/scripts/generate-navigation-template.ts",
feat: fix junction toggle persistence and add type-safe documentation paths (#17421) ## Summary - **Fix junction relation toggle not being saved**: The form schema wasn't tracking the `settings` field, so changes to `junctionTargetFieldId` weren't marked as dirty - **Add type-safe documentation paths**: Generate TypeScript constants from `base-structure.json` to prevent broken documentation links - **Create many-to-many relations documentation**: Step-by-step guide for building many-to-many relations using junction objects - **Update `getDocumentationUrl`**: Now uses shared constants from `twenty-shared` for base URL, default path, and supported languages ## Key Changes ### Junction Toggle Fix - Added `settings` field to the form schema in `SettingsDataModelFieldRelationForm.tsx` - Fixed the toggle to properly merge settings when updating `junctionTargetFieldId` ### Type-Safe Documentation Paths - New constants in `twenty-shared/constants`: - `DOCUMENTATION_PATHS` - All 161 documentation paths as typed constants - `DOCUMENTATION_SUPPORTED_LANGUAGES` - 14 supported languages - `DOCUMENTATION_BASE_URL` / `DOCUMENTATION_DEFAULT_PATH` - Generator script: `yarn docs:generate-paths` - CI integration: Added to `docs-i18n-pull.yaml` workflow ### Documentation - New article: `/user-guide/data-model/how-tos/create-many-to-many-relations` - Updated `/user-guide/data-model/capabilities/relation-fields.mdx` with Lab warning and link ## Test plan - [ ] Verify junction toggle saves correctly when enabled/disabled - [ ] Verify documentation link opens correct localized page - [ ] Verify `yarn docs:generate-paths` regenerates paths correctly
2026-01-25 12:29:20 +00:00
"docs:generate-paths": "tsx packages/twenty-docs/scripts/generate-documentation-paths.ts",
Fix npx nx run start (twenty:server:worker was not triggered) (#8384) twenty:server:worker was not triggered in npx nx run start Co-authored-by: guillim <guillaume@twenty.com>
2024-11-07 14:57:12 +00:00
"start": "npx concurrently --kill-others 'npx nx run-many -t start -p twenty-server twenty-front' 'npx wait-on tcp:3000 && npx nx run twenty-server:worker'"
Added Single Command for Frontend + Backend (#3909) * Added single command * Fix according to review --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-02-13 11:23:29 +00:00
},
Migrate to a monorepo structure (#2909)
2023-12-10 17:10:54 +00:00
"workspaces": {
"packages": [
"packages/twenty-front",
Fix CIs (#3004) * Fix CIs * Fix docs * Fix eslint-build * Move file * Move back * Fix server ci * Fix server ci * Fix server ci * Fix server ci * Deactivate e2e tests * Fix front * Fix front * Fix front * Add twenty-zapier and twenty-utils to the yarn project * fix * fix * Remove pull_request trigger
2023-12-15 14:40:04 +00:00
"packages/twenty-server",
Move emails to dedicated package (#3542) * Add new package * Add twenty-emails package * Use generated files from twenty-emails in twenty-server * Fix deleted file * Import emails templates properly
2024-01-22 15:21:56 +00:00
"packages/twenty-emails",
Setup the foundation for Twenty UI library. (#4423) * feat: create a separate package for twenty-ui, extract the pill component with hard-coded theme values into it, and use the component inside twenty-front to complete the setup * feat: extract the light and the dark theme into twenty-ui and update the AppThemeProvider component inside twenty-front to consume themes from twenty-ui * fix: create a decorator inside preview.tsx to provide a default theme to storybook development server * fix: remove redundant type declarations and revert back the naming convention for theme declarations * fix: introduce a default value for pill label within the story for development server * fix: introduce the nx script into package.json for twenty-ui and resolve imports for theme type within the package * fix: remove the pill component from the twenty-front package along with the story for it * fix: revert the package versions to those before running the nx cli command for storybook init * feat: update readme to include details for building the ui library and starting the storybook development server * fix: include details about twenty-ui inside jest.config for twenty-front to complete front-jest job * - Added preview head for font - Added theme addon for light/dark switch - Added ComponentDecorator --------- Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
2024-03-13 13:21:18 +00:00
"packages/twenty-ui",
Fix CIs (#3004) * Fix CIs * Fix docs * Fix eslint-build * Move file * Move back * Fix server ci * Fix server ci * Fix server ci * Fix server ci * Deactivate e2e tests * Fix front * Fix front * Fix front * Add twenty-zapier and twenty-utils to the yarn project * fix * fix * Remove pull_request trigger
2023-12-15 14:40:04 +00:00
"packages/twenty-utils",
Marketing website POC (#3139) First website POC
2023-12-23 09:08:55 +00:00
"packages/twenty-zapier",
POC: chore: use Nx workspace lint rules (#3163) * chore: use Nx workspace lint rules Closes #3162 * Fix lint * Fix lint on BE * Fix tests --------- Co-authored-by: Charles Bochet <charles@twenty.com>
2024-01-03 22:07:25 +00:00
"packages/twenty-website",
feat: Migrate documentation to Mintlify and implement Helper Agent with search functionality (#15443)
2025-10-31 09:17:54 +00:00
"packages/twenty-docs",
feat(e2e): twenty-e2e-testing with playwright (#6539) ## ISSUE (e2e) - Introduces e2e for twenty - Closes #6360 ## Description - [x] Create Package. - [x] Setup environments such as baseUrl. - [x] ignore CI configuration for now. - [x] write a simple test to check if table is visible in companies tab. ### Running test with UI ``` yarn run test:e2e:ui ``` https://github.com/user-attachments/assets/a7b7ae35-8898-461e-8c7c-d3e4e9515aeb ### Running all test and seeing report ``` yarn run test:e2e yarn run test:e2e:report ``` https://github.com/user-attachments/assets/2558a1f9-97cc-4f06-86f0-806f207eac5a --------- Co-authored-by: Lucas Bordeau <bordeau.lucas@gmail.com>
2024-08-14 15:23:32 +00:00
"packages/twenty-e2e-testing",
Add Twenty Shared & Fix profile image rendering (#8841) PR Summary: 1. Added `Twenty Shared` Package to centralize utilitiies as mentioned in #8942 2. Optimization of `getImageAbsoluteURI.ts` to handle edge cases ![image](https://github.com/user-attachments/assets/c72a3061-6eba-46b8-85ac-869f06bf23c0) --------- Co-authored-by: Antoine Moreaux <moreaux.antoine@gmail.com> Co-authored-by: Charles Bochet <charles@twenty.com>
2024-12-17 08:24:21 +00:00
"packages/twenty-shared",
Add twenty-sdk (#15208)
2025-10-20 13:54:08 +00:00
"packages/twenty-sdk",
First Application POC (#14382) Quick proof of concept for twenty-apps + twenty-cli, with local development / hot reload Let's discuss it! https://github.com/user-attachments/assets/c6789936-cd5f-4110-a265-863a6ac1af2d
2025-09-10 13:12:38 +00:00
"packages/twenty-apps",
"packages/twenty-cli",
Merge twenty-cli into twenty-sdk (#16150) - Moves twenty-cli content into twenty-sdk - add a new twenty-sdk:0.1.0 version - this new twenty-sdk exports a cli command called 'twenty' (like twenty-cli before) - deprecates twenty-cli - simplify app init command base-project - use `twenty-sdk:0.1.0` in base project - move the "twenty-sdk/application" barrel to "twenty-sdk" - add `create-twenty-app` package <img width="1512" height="919" alt="image" src="https://github.com/user-attachments/assets/007bef45-4e71-419a-9213-cebed376adbf" /> <img width="1506" height="929" alt="image" src="https://github.com/user-attachments/assets/3de2fec6-1624-4923-ae13-f4e1cf165eb5" />
2025-12-01 10:44:35 +00:00
"packages/create-twenty-app",
Migrate from ESLint to OxLint (#18443) ## Summary Fully replaces ESLint with OxLint across the entire monorepo: - **Replaced all ESLint configs** (`eslint.config.mjs`) with OxLint configs (`.oxlintrc.json`) for every package: `twenty-front`, `twenty-server`, `twenty-emails`, `twenty-ui`, `twenty-shared`, `twenty-sdk`, `twenty-zapier`, `twenty-docs`, `twenty-website`, `twenty-apps/*`, `create-twenty-app` - **Migrated custom lint rules** from ESLint plugin format to OxLint JS plugin system (`@oxlint/plugins`), including `styled-components-prefixed-with-styled`, `no-hardcoded-colors`, `sort-css-properties-alphabetically`, `graphql-resolvers-should-be-guarded`, `rest-api-methods-should-be-guarded`, `max-consts-per-file`, and Jotai-related rules - **Migrated custom rule tests** from ESLint `RuleTester` + Jest to `oxlint/plugins-dev` `RuleTester` + Vitest - **Removed all ESLint dependencies** from `package.json` files and regenerated lockfiles - **Updated Nx targets** (`lint`, `lint:diff-with-main`, `fmt`) in `nx.json` and per-project `project.json` to use `oxlint` commands with proper `dependsOn` for plugin builds - **Updated CI workflows** (`.github/workflows/ci-*.yaml`) — no more ESLint executor - **Updated IDE setup**: replaced `dbaeumer.vscode-eslint` with `oxc.oxc-vscode` extension, configured `source.fixAll.oxc` and format-on-save with Prettier - **Replaced all `eslint-disable` comments** with `oxlint-disable` equivalents across the codebase - **Updated docs** (`twenty-docs`) to reference OxLint instead of ESLint - **Renamed** `twenty-eslint-rules` package to `twenty-oxlint-rules` ### Temporarily disabled rules (tracked in `OXLINT_MIGRATION_TODO.md`) | Rule | Package | Violations | Auto-fixable | |------|---------|-----------|-------------| | `twenty/sort-css-properties-alphabetically` | twenty-front | 578 | Yes | | `typescript/consistent-type-imports` | twenty-server | 3814 | Yes | | `twenty/max-consts-per-file` | twenty-server | 94 | No | ### Dropped plugins (no OxLint equivalent) `eslint-plugin-project-structure`, `lingui/*`, `@stylistic/*`, `import/order`, `prefer-arrow/prefer-arrow-functions`, `eslint-plugin-mdx`, `@next/eslint-plugin-next`, `eslint-plugin-storybook`, `eslint-plugin-react-refresh`. Partial coverage for `jsx-a11y` and `unused-imports`. ### Additional fixes (pre-existing issues exposed by merge) - Fixed `EmailThreadPreview.tsx` broken import from main rename (`useOpenEmailThreadInSidePanel`) - Restored truthiness guard in `getActivityTargetObjectRecords.ts` - Fixed `AgentTurnResolver` return types to match entity (virtual `fileMediaType`/`fileUrl` are resolved via `@ResolveField()`) ## Test plan - [x] `npx nx lint twenty-front` passes - [x] `npx nx lint twenty-server` passes - [x] `npx nx lint twenty-docs` passes - [x] Custom oxlint rules validated with Vitest: `npx nx test twenty-oxlint-rules` - [x] `npx nx typecheck twenty-front` passes - [x] `npx nx typecheck twenty-server` passes - [x] CI workflows trigger correctly with `dependsOn: ["twenty-oxlint-rules:build"]` - [x] IDE linting works with `oxc.oxc-vscode` extension
2026-03-06 00:03:50 +00:00
"packages/twenty-oxlint-rules"
Migrate to a monorepo structure (#2909)
2023-12-10 17:10:54 +00:00
]
chore: cleanup repository root structure (#17147) ## Summary This PR reduces clutter at the repository root to improve navigation on GitHub. The README is now visible much sooner when browsing the repo. ## Changes ### Deleted from root - `nx` wrapper script → use `npx nx` instead - `render.yaml` → no longer used - `jest.preset.js` → inlined `@nx/jest/preset` directly in each package's jest.config - `.prettierrc` → moved config to `package.json` - `.prettierignore` → patterns already covered by `.gitignore` ### Moved/Consolidated | From | To | |------|-----| | `Makefile` | `packages/twenty-docker/Makefile` (merged) | | `crowdin-app.yml` | `.github/crowdin-app.yml` | | `crowdin-docs.yml` | `.github/crowdin-docs.yml` | | `.vale.ini` | `.github/vale.ini` | | `tools/eslint-rules/` | `packages/twenty-eslint-rules/` | | `eslint.config.react.mjs` | `packages/twenty-front/eslint.config.react.mjs` | ## Result Root items reduced from ~32 to ~22 (folders + files). ## Files updated - GitHub workflow files updated to reference new crowdin config paths - Jest configs updated to use `@nx/jest/preset` directly - ESLint configs updated with new import paths - `nx.json` updated with new paths - `package.json` now includes prettier config and updated workspace paths - Dockerfile updated with new eslint-rules path
2026-01-14 12:56:30 +00:00
},
"prettier": {
"singleQuote": true,
"trailingComma": "all",
"endOfLine": "lf"
Migrate to a monorepo structure (#2909)
2023-12-10 17:10:54 +00:00
}
}
Reference in a new issue Copy permalink