@mkappelhof/ts-config 2.0.1 → 2.1.1

package/AGENTS.md

@@ -11,6 +11,7 @@ Check `extends` in the project's `tsconfig.json`:
 | `@mkappelhof/ts-config/next.json` | Next.js apps | ESM, bundler resolution, type-check only (`noEmit`) |
 | `@mkappelhof/ts-config/react.json` | React apps and libraries built with a bundler (Vite, etc.) | ESM, bundler resolution, type-check only (`noEmit`) |
 | `@mkappelhof/ts-config/node.json` | Node.js 24+ services, scripts and CLIs | Native Node ESM (`NodeNext`) |
+| `@mkappelhof/ts-config/nest.json` | NestJS services | CommonJS, legacy decorators (`experimentalDecorators`, `emitDecoratorMetadata`) |
 | `@mkappelhof/ts-config/library.json` | React libraries built with a bundler that publish type declarations | ESM, bundler resolution, declaration emit only (`emitDeclarationOnly`) |
 | `@mkappelhof/ts-config/astro.json` | Astro sites and apps | ESM, bundler resolution, type-check only (`noEmit`), `jsx: "preserve"` |
 
@@ -52,6 +53,12 @@ Check `extends` in the project's `tsconfig.json`:
 - Top-level `await` is allowed.
 - `@types/node` must be installed. It is the only ambient types package loaded (`"types": ["node"]`); add others to `types` in the project's `tsconfig.json`.
 
+## nest.json
+
+- CommonJS, not ESM: `module`/`moduleResolution` are `commonjs`/`node`. Use `require`/`module.exports` semantics via `import`/`export` as Nest's CLI generates them; there's no `"type": "module"` requirement and no file-extension-in-import rule.
+- `experimentalDecorators` and `emitDecoratorMetadata` are on, and `erasableSyntaxOnly`/`verbatimModuleSyntax` are off (unlike every other preset in this package). Parameter properties (`constructor(private readonly foo: FooService) {}`) and decorators (`@Injectable()`, `@Controller()`, etc.) are expected and fine to use here — this is the one preset where that's true.
+- Run `nest build` (or `tsc -p tsconfig.build.json` if the project has one) to compile; don't switch the project to `tsc --noEmit`-only workflows.
+
 ## astro.json
 
 - `jsx` is `"preserve"`, not `"react-jsx"`. `.astro` files are their own syntax, compiled by the Astro compiler, not `tsc`; this setting only matters for `.tsx` islands (e.g. from `@astrojs/react`), and Astro's Vite plugin handles their actual JSX transform regardless of this setting.

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @mkappelhof/ts-config
 
+## 2.1.1
+
+### Patch Changes
+
+- bb566eb: Update settings
+
+## 2.1.0
+
+### Minor Changes
+
+- 3c4c6b4: Add `nest.json` preset for NestJS services: CommonJS, `experimentalDecorators`/`emitDecoratorMetadata` on, `erasableSyntaxOnly`/`verbatimModuleSyntax` off so parameter properties and decorator-based DI work.
+
 ## 2.0.1
 
 ### Patch Changes

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Maurice
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -7,6 +7,7 @@ Shared `tsconfig.json` presets for TypeScript 6 and 7.
 | `@mkappelhof/ts-config/next.json` | Next.js applications |
 | `@mkappelhof/ts-config/react.json` | React apps and libraries built with a bundler (Vite, Rsbuild, etc.) |
 | `@mkappelhof/ts-config/node.json` | Node.js 24+ services, scripts and CLIs (native ESM) |
+| `@mkappelhof/ts-config/nest.json` | NestJS services (CommonJS, legacy decorators) |
 | `@mkappelhof/ts-config/library.json` | React libraries built with a bundler that publish type declarations |
 | `@mkappelhof/ts-config/astro.json` | Astro sites and apps |
 
@@ -83,6 +84,25 @@ Set `"type": "module"` in your `package.json`, then:
 
 The code only uses erasable TypeScript syntax, so you can run it directly with `node src/index.ts` or compile it with `tsc`. Relative imports must include an extension (`./util.ts`), which is rewritten to `.js` on emit.
 
+### NestJS
+
+```sh
+pnpm add -D @types/node
+```
+
+```JSON
+{
+  "extends": "@mkappelhof/ts-config/nest.json",
+  "compilerOptions": {
+    "outDir": "dist",
+    "rootDir": "src"
+  },
+  "include": ["src"]
+}
+```
+
+Unlike the other presets, this one stays on CommonJS and legacy decorators (`experimentalDecorators`, `emitDecoratorMetadata`) with `erasableSyntaxOnly` and `verbatimModuleSyntax` off, since Nest's constructor-based DI relies on parameter properties and decorator metadata. Build with `nest build` (or `tsc -p tsconfig.build.json`).
+
 ### Astro
 
 ```JSON

package/nest.json

@@ -0,0 +1,24 @@
+{
+  "$schema": "https://www.schemastore.org/tsconfig",
+  "display": "NestJS",
+  "compilerOptions": {
+    "target": "ES2023",
+    "lib": [
+      "ES2023"
+    ],
+    "module": "commonjs",
+    "moduleResolution": "node",
+    "moduleDetection": "force",
+    "types": [
+      "node"
+    ],
+    "resolveJsonModule": true,
+    "experimentalDecorators": true,
+    "emitDecoratorMetadata": true,
+    "strict": true,
+    "noUncheckedIndexedAccess": true,
+    "noImplicitOverride": true,
+    "noFallthroughCasesInSwitch": true,
+    "skipLibCheck": true
+  }
+}

package/package.json

@@ -1,13 +1,10 @@
 {
   "name": "@mkappelhof/ts-config",
-  "version": "2.0.1",
+  "version": "2.1.1",
   "main": "base.json",
   "license": "MIT",
   "repository": "git@github.com:mkappelhof/frontend-tools.git",
   "author": "Maurice Kappelhof <maurice@mauricekappelhof.nl>",
-  "scripts": {
-    "test": "echo 'No test step'"
-  },
   "peerDependencies": {
     "typescript": "^6.0.0 || ^7.0.0"
   },
@@ -15,5 +12,9 @@
     "typescript",
     "tsconfig",
     "config"
-  ]
+  ],
+  "scripts": {
+    "test": "echo 'No test step'",
+    "clean": "rimraf node_modules"
+  }
 }

package/.turbo/turbo-build.log

@@ -1,13 +0,0 @@
-
-> @mkappelhof/ts-config@1.0.7 build /Users/mauricekappelhof/Dev/frontend-tools/packages/ts-config
-> rollup -c
-
-
-./base.json → ./dist/base.json...
-(!) Mixing named and default exports
-https://rollupjs.org/configuration-options/#output-exports
-The following entry modules are using named and default exports together:
-base.json
-
-Consumers of your bundle will have to use chunk.default to access their default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
-created ./dist/base.json in 22ms