tsconfig, biome and editorconfig as a dependency — never as a copy.
$ npm i -D @frontierjs/config
One line in your tsconfig.json
A copied config is frozen at the moment it was written. A dependency moves when the framework does, which is the entire difference between a template and a package.
{ "extends": "@frontierjs/config/tsconfig" }Linter only, and the refusal is measured
This house aligns columns and no formatter can express that. The code the scaffolder writes is aligned, so the first format run would rewrite the app the scaffold had just produced.
A linter owns generic JavaScript
It reads neither .mesa nor .lite, on purpose: everything derived from the seed is graded by the framework’s own checks, which can see the schema the linter cannot.
The rest of the stack