github-mirror/n8n
1
0
Fork 0
mirror of https://github.com/n8n-io/n8n.git synced 2026-10-17 05:29:44 +02:00
Code Issues Actions 14 Packages Projects Releases Wiki Activity Graph
a41c8c46e7
n8n/packages/modules
History
ocdejong 2ec6ac7c9c
feat(editor): Show each policy violation with its scope when a save, publish or execution is refused (#39263) 
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-28 08:56:57 +00:00
..
insights/frontend build: Upgrade Vitest to v5 (no-changelog) (#39674) 2026-09-28 07:54:06 +00:00
instance-registry/frontend 🚀 Release 2.41.0 (#39228) 2026-09-22 07:18:44 +00:00
otel/frontend 🚀 Release 2.41.0 (#39228) 2026-09-22 07:18:44 +00:00
type-availability-policies/frontend feat(editor): Show each policy violation with its scope when a save, publish or execution is refused (#39263) 2026-09-28 08:56:57 +00:00
README.md ci: Split the packages/modules test filters into frontend and backend (no-changelog) (#38121) 2026-09-09 07:43:57 +00:00

README.md

Modules

Feature modules carved out of packages/frontend/editor-ui. Each one is a workspace package at <name>/frontend: source-only (main: "src/index.ts", no dist), consumed by the editor-ui shell through Vite aliases.

<name>/backend is a reserved path rather than a workspace package — the backend runtime discovers modules under packages/cli/src/modules/<name>. The extra nesting level is what lets both halves of a module sit together later.

packages/modules itself stays tracked even when it holds nothing: turbo rejects a --filter whose directory does not exist.

CI splits the two halves by path. The frontend jobs select packages/modules/*/frontend. The backend jobs exclude that same path instead of all of packages/modules, so a <name>/backend package gets backend CI on the day it appears. Both filters live in the root test:ci:* scripts and in the two backend jobs in .github/workflows/test-unit-reusable.yml.