Building a modern alternative to Salesforce, powered by the community.
Go to file
Thaïs 992602b307
fix: fix storybook build cache not being used by tests in CI (#5451)
TL;DR:
- removed `--configuration={args.scope}` from `storybook:static:test`
for the `storybook:static` part, as it was making `front-sb-test` jobs
in CI not reuse the cache from the `front-sb-build` job and re-build
storybook every time.
- replaced it with a new `test` configuration which optimizes storybook
build for tests and builds storybook 2x faster.

## Fix storybook:build cache usage in CI

`storybook:static:test` executes two scripts in parallel:
1. `storybook:static`, which depends on `storybook:build`
1.a. it builds storybook first with `storybook:build`, the output
directory is `storybook-static`.
1.b. then it launches an `http-server`, using what has been built in
`storybook-static`
2. `storybook:test` to execute tests (needs the storybook http-server to
be running)

When passing `--configuration=pages` or `--configuration=modules` to
`storybook:static` from step 1, those configurations are passed to the
`storybook:build` script from step 1.a as well.

But for Nx `storybook:build` and `storybook:build --configuration=pages`
(or `modules`) are not the same command, therefore one does not reuse
the cache of the other because they could output completely different
things.

As `front-sb-test` jobs are passing `--configuration={args.scope}` to
`storybook:static`, the cache of the previously executed
`storybook:build` (from `front-sb-build`) is not reused and therefore
each job re-builds Storybook with its own scope, which increases CI
time.

### Solution

- Removed scope configurations from `storybook:static` and
`storybook:build` scripts to avoid confusion.
- `storybook:test` and `storybook:dev` can keep scope configurations as
they can be useful and this doesn't impact storybook build cache in CI.

### Improve Storybook build time for testing

Added the `test` configuration to `storybook:build` and
`storybook:static` which makes Storybook build time 2x faster. It
disables addons that slow down build time and are not used in tests.
2024-05-17 16:05:31 +02:00
.github fix: fix storybook build cache not being used by tests in CI (#5451) 2024-05-17 16:05:31 +02:00
.nx chore: upgrade Nx to v18.1.3 (#4706) 2024-04-01 13:16:50 +02:00
.vscode Fix sync metadata script (#5253) 2024-05-02 15:50:40 +02:00
.yarn/releases Fix docker install (#2925) 2023-12-11 13:36:24 +01:00
packages fix: fix storybook build cache not being used by tests in CI (#5451) 2024-05-17 16:05:31 +02:00
tools/eslint-rules chore: use Nx affected tasks in CI (#5110) 2024-04-30 16:28:25 +02:00
.dockerignore feat: merge front and server dockerfiles and optimize build (#4589) 2024-03-21 19:22:21 +01:00
.eslintrc.cjs Adds no-debugger rule to root eslint config file (#5312) 2024-05-07 11:07:51 +02:00
.eslintrc.react.cjs fix: fix storybook:build memory allocation error in CI (#5284) 2024-05-03 19:19:21 +02:00
.gitignore fix: fix storybook build script not found by Chromatic (#5235) 2024-05-02 16:15:36 +02:00
.nvmrc Embrace nx monorepo structure with root package.json (#3255) 2024-01-05 14:59:58 +01:00
.prettierignore POC: chore: use Nx workspace lint rules (#3163) 2024-01-03 23:07:25 +01:00
.prettierrc POC: chore: use Nx workspace lint rules (#3163) 2024-01-03 23:07:25 +01:00
.vale.ini Fix vale ci (#3353) 2024-01-10 17:05:23 +01:00
.yarnrc.yml Fix docker install (#2925) 2023-12-11 13:36:24 +01:00
install.sh Typo in docker compose up hint (#4866) 2024-04-07 11:14:20 +02:00
jest.config.js POC: chore: use Nx workspace lint rules (#3163) 2024-01-03 23:07:25 +01:00
jest.preset.js POC: chore: use Nx workspace lint rules (#3163) 2024-01-03 23:07:25 +01:00
LICENSE Update LICENSE (#714) 2023-07-17 10:08:37 +02:00
Makefile Re-add docker-compose up command 2024-01-13 11:02:00 +01:00
nx Migrate to a monorepo structure (#2909) 2023-12-10 18:10:54 +01:00
nx.json fix: fix storybook build cache not being used by tests in CI (#5451) 2024-05-17 16:05:31 +02:00
package.json chore: add nx/project.json to twenty-chrome-extension (#5217) 2024-05-06 11:33:48 +02:00
README.md Update README.md (#5345) 2024-05-11 09:30:03 +02:00
render.yaml File token chores (#4664) 2024-03-26 13:42:09 +01:00
tsconfig.base.json refactor: move Checkmark, Avatar, Chip and Tooltip to twenty-ui (#4946) 2024-04-15 12:05:06 +02:00
yarn.lock chore: add nx/project.json to twenty-chrome-extension (#5217) 2024-05-06 11:33:48 +02:00


Twenty logo

The #1 Open-Source CRM

Tailored to your unique business needs

🌐 Website · 📚 Documentation · Discord · Figma


Companies view


Weve spent thousands of hours grappling with traditional CRMs like Pipedrive and Salesforce to align them with our business needs, only to end up frustrated — customizations are complex and the closed ecosystems of these platforms can feel restrictive.

We felt the need for a CRM platform that empowers rather than constrains. We believe the next great CRM will come from the open-source community. Weve packed Twenty with powerful features to give you full control and help you run your business efficiently.


Demo

Go to demo.twenty.com and login with the following credentials:

email: noah@demo.dev
password: Applecar2025

See also:
🚀 Self-hosting
🖥️ Local Setup

Why Choose Twenty?

We understand that the CRM landscape is vast. So why should you choose us?

⛓️ Full control, Full Freedom: Contribute, self-host, fork. Break free from vendor lock-in and join us in shaping the open future of CRM.

📊 Data, Your Way: The days when the role of CRM platforms was to shift manual data entries to a database are over. Now, the data is already there. CRM 2.0 should be built around your data, allowing you to access and visualize any existing sources, not forcing you to retrofit your data into predefined objects on a remote cloud.

🎨 Effortlessly Intuitive: We set out to create something that we ourselves would always enjoy using. The main application draws inspiration from Notion, a tool known for its user-friendly interface and customization capabilities.


What You Can Do With Twenty

We're currently in the development phase of Twenty's alpha version.

Please feel free to flag any specific need you have need by creating an issue.

Below are some features we have implemented to date:

Add, filter, sort, edit, and track customers:

Companies view

Create one or several opportunities for each company:

Companies view

Track deals effortlessly with the email integration:

Companies view

Tailor your data model to meet business needs:

Companies view

See rich notes displayed in a timeline:

Companies view

Create tasks on records

Companies view

Companies view

Connect your CRM to all your tools through our APIs and Webhooks.

Companies view


What's In Store

Heres what you can look forward to:

Frequent updates: Were shipping fast! Expect regular updates and new features that enhance your experience.

🔗 Extensibility: Were putting the power in your hands. Soon, youll have the tools to extend and customize Twenty with plugins and more.


Join the Community