Document that package.json aliases may target only direct subfolders of src #21
@@ -24,6 +24,8 @@ Node + Vite+ migration (PR #20, `node-migration`, 2026-10-15/16):
|
||||
dependency of this repo's TypeScript.
|
||||
- **No `@cunarist/eslint-plugin-*`.** The Deno setup enabled no plugin, so
|
||||
this repo depends on none and CI passes without them being published.
|
||||
Planned (2026-10-17): once the plugins are on npm, add
|
||||
`@cunarist/eslint-plugin-modules` here for its import checks.
|
||||
- **Stricter input checks were accepted** in the migration: Gitea `/user` and
|
||||
comment responses, the runtime manifest, and the outcome's profile type are
|
||||
validated; some type errors became `TypeError` with the same messages.
|
||||
|
||||
@@ -19,7 +19,7 @@ convention, see the last section):
|
||||
folder's `index.ts` owns that folder and everything below it; an alias to
|
||||
any other file owns only that file.
|
||||
- **No overlap.** No file may be owned by 2 aliases: no alias inside another
|
||||
alias's area, and no 2 aliases with the same target. the modules plugin's
|
||||
alias's area, and no 2 aliases with the same target. The modules plugin's
|
||||
`enforce-layer-order` reports it once at the top of every file 2 aliases
|
||||
claim. Fix by merging the aliases or moving files apart.
|
||||
- **Outside an area, only the exact alias reaches it.** A deeper alias
|
||||
|
||||
Reference in New Issue
Block a user