@infinitetoken/tsconfig 0.2.0 → 0.3.0

package/README.md

@@ -1,6 +1,6 @@
 # @infinitetoken/tsconfig
 
-Shared base `tsconfig.json` for InfiniteToken TypeScript packages. Holds the compiler flags every repo agrees on (strictness, declaration output, consistent casing). Also ships an opt-in `tsup` build config factory (`@infinitetoken/tsconfig/tsup`) — see [tsup config](#tsup-config) below.
+Shared base `tsconfig.json` for InfiniteToken TypeScript packages. Holds the compiler flags every repo agrees on (strictness, declaration output, consistent casing). Also ships opt-in `tsup` build config factories for a library, a CLI, or both — see [tsup config](#tsup-config) below.
 
 ## Presets
 
@@ -32,18 +32,48 @@ That's the whole file for a typical Node/kit package — every other compiler op
 
 ## tsup config
 
-Opt-in — only relevant if the package builds with `tsup`. Unlike `tsconfig.json`, a `tsup.config` file is executable code with no path-resolution sharing limitation, so this is a plain factory function — same shape as `@infinitetoken/jest-config`'s presets, a bare function you call, nothing invoked by name off an object. Use a `tsup.config.cjs` (not `.ts`) so it loads directly with `require()` instead of going through tsup's ESM-bundling loader.
+Opt-in — only relevant if the package builds with `tsup`. Unlike `tsconfig.json`, a `tsup.config` file is executable code with no path-resolution sharing limitation, so these are plain factory functions — same shape as `@infinitetoken/jest-config`'s presets, a bare function you call, nothing invoked by name off an object. Use a `tsup.config.cjs` (not `.ts`) so it loads directly with `require()` instead of going through tsup's ESM-bundling loader. Pick the export that matches what the package actually ships:
+
+| Export | Use for |
+| --- | --- |
+| `@infinitetoken/tsconfig/tsup/lib` | A library with no CLI — one entry, cjs+esm, declarations, cleans `dist/` |
+| `@infinitetoken/tsconfig/tsup/cli` | A CLI with no separate library export (`main`/`exports` point straight at the built bin) — one entry, esm-only, Node shebang banner, no declarations |
+| `@infinitetoken/tsconfig/tsup/lib-cli` | A package that ships both — a real, separately-importable library **and** a CLI bin — the library entry (cjs+esm, declarations, cleans `dist/`) plus the CLI entry (esm-only, shebang, no declarations) |
+
+The plain library case — one entry point, nothing else:
+
+```js
+// tsup.config.cjs
+module.exports = require('@infinitetoken/tsconfig/tsup/lib')()
+```
+
+Pass a different entry or override anything tsup accepts: `require('@infinitetoken/tsconfig/tsup/lib')('src/main.ts', { minify: true })`.
+
+A CLI-only package:
 
 ```js
 // tsup.config.cjs
-module.exports = require('@infinitetoken/tsconfig/tsup')()
+module.exports = require('@infinitetoken/tsconfig/tsup/cli')()
 ```
 
-That's the whole file for one library entry point — cjs+esm, with declarations, cleaning `dist/` first. Pass a different entry or override anything tsup accepts: `require('@infinitetoken/tsconfig/tsup')('src/main.ts', { minify: true })`.
+A package with both a library and a CLI:
 
-A package with more than one entry point (a library plus a CLI bin, say) isn't covered by this factory yet — write `tsup.config.cjs` by hand with `tsup`'s own `defineConfig([...])` for that case, same as before this package existed.
+```js
+// tsup.config.cjs
+module.exports = require('@infinitetoken/tsconfig/tsup/lib-cli')()
+```
+
+That returns the full two-entry array (`createTsupLibCliConfig(libEntry?, cliEntry?, { lib?, cli? })` — defaults to `src/index.ts` / `src/cli.ts`). A package with an extra entry beyond those two (e.g. a separate subpath export) can spread it and append its own:
+
+```js
+// tsup.config.cjs
+const { defineConfig } = require('tsup')
+const createTsupLibCliConfig = require('@infinitetoken/tsconfig/tsup/lib-cli')
+
+module.exports = defineConfig([...createTsupLibCliConfig(), { entry: ['src/shapes.ts'], format: ['esm', 'cjs'], dts: true }])
+```
 
-`createTsupConfig` defaults `dts: true` — a package doing `tsup && tsc --emitDeclarationOnly` as two separate steps (rather than letting tsup's own entry-scoped `dts` option handle it) will end up shipping declarations for every file `tsconfig.json`'s `include` matches, `__tests__` included, not just the real entry point.
+All three default `dts: true` on every entry that represents real importable code (never on a CLI entry — nobody imports a bin as a typed library) — a package doing `tsup && tsc --emitDeclarationOnly` as two separate steps, rather than letting tsup's own entry-scoped `dts` option handle it, will end up shipping declarations for every file `tsconfig.json`'s `include` matches, `__tests__` included, not just the real entry point.
 
 ## Release
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@infinitetoken/tsconfig",
-  "version": "0.2.0",
+  "version": "0.3.0",
   "description": "Shared base tsconfig for InfiniteToken TypeScript packages, with an opt-in tsup build config",
   "keywords": [
     "config",
@@ -21,20 +21,18 @@
   "sideEffects": false,
   "type": "commonjs",
   "exports": {
-    ".": "./tsconfig.json",
-    "./node": "./node.json",
+    ".": "./src/tsconfig.json",
+    "./node": "./src/node.json",
     "./package.json": "./package.json",
-    "./react-native": "./react-native.json",
-    "./server": "./server.json",
-    "./tsconfig.json": "./tsconfig.json",
-    "./tsup": "./tsup.cjs"
+    "./react-native": "./src/react-native.json",
+    "./server": "./src/server.json",
+    "./tsconfig.json": "./src/tsconfig.json",
+    "./tsup/cli": "./src/tsup/cli.cjs",
+    "./tsup/lib": "./src/tsup/lib.cjs",
+    "./tsup/lib-cli": "./src/tsup/lib-cli.cjs"
   },
   "files": [
-    "tsconfig.json",
-    "node.json",
-    "react-native.json",
-    "server.json",
-    "tsup.cjs"
+    "src"
   ],
   "scripts": {
     "fix": "eslint . --fix",

package/src/tsup/cli.cjs

@@ -0,0 +1,24 @@
+const { defineConfig } = require('tsup')
+
+/**
+ * A CLI-only package with no separate library export — the bin IS the package
+ * (no `dts`: there's no typed API for anyone to import). ESM-only with a Node
+ * shebang banner. Modeled on the CLI half of the fleet's package+CLI packages,
+ * not on any existing CLI-only package — those still need aligning onto this
+ * shape, not the other way around.
+ *
+ * @param {string|string[]} [entry]
+ * @param {import('tsup').Options} [overrides]
+ * @returns {import('tsup').Options}
+ */
+function createTsupCliConfig(entry = 'src/cli.ts', overrides = {}) {
+  return defineConfig({
+    entry: Array.isArray(entry) ? entry : [entry],
+    format: ['esm'],
+    banner: { js: '#!/usr/bin/env node' },
+    clean: true,
+    ...overrides
+  })
+}
+
+module.exports = createTsupCliConfig

package/src/tsup/lib-cli.cjs

@@ -0,0 +1,33 @@
+const { defineConfig } = require('tsup')
+
+/**
+ * A package that also ships a CLI bin: one library entry (cjs+esm, declarations,
+ * cleans dist/ first) plus one CLI entry (esm-only, Node shebang banner, no
+ * declarations — nobody imports a bin as a typed library). Returns the full
+ * two-entry array; a package with more entries than this (e.g. an extra
+ * subpath) can spread it and append its own: `[...createTsupLibCliConfig(), extraEntry]`.
+ *
+ * @param {string|string[]} [libEntry]
+ * @param {string|string[]} [cliEntry]
+ * @param {{ lib?: import('tsup').Options, cli?: import('tsup').Options }} [overrides]
+ * @returns {import('tsup').Options[]}
+ */
+function createTsupLibCliConfig(libEntry = 'src/index.ts', cliEntry = 'src/cli.ts', overrides = {}) {
+  return defineConfig([
+    {
+      entry: Array.isArray(libEntry) ? libEntry : [libEntry],
+      format: ['cjs', 'esm'],
+      dts: true,
+      clean: true,
+      ...overrides.lib
+    },
+    {
+      entry: Array.isArray(cliEntry) ? cliEntry : [cliEntry],
+      format: ['esm'],
+      banner: { js: '#!/usr/bin/env node' },
+      ...overrides.cli
+    }
+  ])
+}
+
+module.exports = createTsupLibCliConfig