Charles Bochet
192a842f57
## Problem Building `twenty-website-new` in any environment that does **not** also include `twenty-website` (e.g. the Docker image used by the deployment workflow) fails with: ``` Error: Turbopack build failed with 99 errors: Error evaluating Node.js code Error: Cannot find module 'next/babel' Require stack: - /app/node_modules/@babel/core/lib/config/files/plugins.js - ... - /app/node_modules/babel-merge/src/index.js - /app/packages/twenty-website-new/node_modules/@wyw-in-js/transform/lib/plugins/babel-transform.js - /app/packages/twenty-website-new/node_modules/next-with-linaria/lib/loaders/turbopack-transform-loader.js ``` ## Root cause `packages/twenty-website-new/wyw-in-js.config.cjs` references presets by bare name: ```js presets: ['next/babel', '@wyw-in-js'], ``` These options flow through [`babel-merge`](https://github.com/cellog/babel-merge/blob/master/src/index.js#L11), which calls `@babel/core`'s `resolvePreset(name)` **without** a `dirname` argument. With no `dirname`, `@babel/core` falls back to `require.resolve(id)` from its own file location — so resolution starts at `node_modules/@babel/core/...` and only walks parent `node_modules` directories from there, never down into individual workspace packages. In a normal local install both presets happen to be hoisted to the workspace root (because `twenty-website` pins `next@^14` and wins the hoist), so resolution succeeds by accident. In the single-workspace Docker build only `twenty-website-new` is present, so `next` (16.1.7) and `@wyw-in-js/babel-preset` are nested in `packages/twenty-website-new/node_modules` and Babel cannot reach them — hence the failure. ## Fix Pre-resolve both presets with `require.resolve(...)` in the wyw-in-js config so Babel receives absolute paths and resolution becomes independent of hoisting layout. ## Verification - `yarn nx build twenty-website-new` — passes locally with the full workspace - Reproduced the original failure with a simulated single-workspace install (only `twenty-website-new` and `twenty-oxlint-rules` present), confirmed it fails on `main` and passes with this patch - This unblocks the `twenty-infra` `Deploy Website New` workflow ([related infra PR](https://github.com/twentyhq/twenty-infra/pull/586)) Made with [Cursor](https://cursor.com)
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Linaria and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!