Conversation
v4 dropped fsevents native binding, falling back to recursive fs.watch which opens fd-per-dir on macOS and hits EMFILE on large monorepos. Replace internal chokidar/handler.js EventName import with local type since v3 has no such module.
📊 API Changes ReportGraphQL Schema ChangesGraphQL Schema Changes[error] Error: Unable to read JSON file: /home/runner/work/twenty/twenty/main-schema-introspection.json: Not valid JSON content GraphQL Metadata Schema ChangesGraphQL Metadata Schema Changes[error] Error: Unable to read JSON file: /home/runner/work/twenty/twenty/main-metadata-schema-introspection.json: Not valid JSON content REST API Analysis ErrorError OutputREST Metadata API Analysis ErrorError Output |
Domain equality is unreliable at universities and other institutional domains where unrelated members share an address space. Gate filterOutInternals and the contact-self/workspace-member filter on a Hipolabs-backed institutional domain list so legitimate collaborators are not silently dropped during import.
…l accounts" This reverts commit 4250890.
|
🚀 Preview Environment Ready! Your preview environment is available at: http://bore.pub:11828 This environment will automatically shut down after 5 hours. |
fixes
EMFILEby downgrading chokidar to v3root cause is v4 removed kernel level FSEvents on macOS and instead uses
node:fs.watchwhich doesn't scales for a repo of our sizeSeems to be working well, even survives multiple hot reloads after editing files