Repository navigation
@notils/cli v0.6.1 — monorepo add fixes
@notils/cli v0.6.1
Fixes for notils add in a monorepo, all reported from a real project running
0.6.0. Standalone targets were unaffected.
If you added a package with 0.6.0, re-run notils add <name> after upgrading —
your source files are kept, and the manifest and tsconfig are regenerated correctly.
Fixed
-
A package added to a monorepo now has a working
tsconfig.json. It extended
a hardcoded"../../tsconfig.json", which a create-notils monorepo does not have
— its packages extend@<scope>/config/*presets. That producedTS5083: Cannot read file '<root>/tsconfig.json', and because a brokenextendsinherits no
compiler options, the package then also failed onstrict, JSX, and module
resolution. -
The generated manifest was missing
scriptsanddevDependencies. Without
@<scope>/configtheextendshad no reason to resolve; and a package with no
typecheckscript is silently skipped by Turborepo, which is why a genuinely
broken package still reported a passingturbo run typecheck. -
External dependencies are declared on the package that imports them. They
were installed at the workspace root instead, sozodended up in the root
dependencieswhilepackages/auth-customdeclared nothing. The offered install
now runs in each package's own directory. -
add appasks whether you want a fresh or demo app, instead of silently
defaulting to fresh.--no-demois now accepted rather than rejected as unknown.
Not changed
The template ref stays v0.6.0 — this release is CLI code only, so there is no new
template content to fetch.