@infinitetoken/tsconfig 0.1.4 → 0.2.0

package/README.md

@@ -32,29 +32,18 @@ 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, not a JSON preset. Use a `tsup.config.cjs` (not `.ts`) so it loads directly with `require()` instead of going through tsup's ESM-bundling loader.
-
-The common case — one library entry, cjs+esm, with declarations, cleaning `dist/` first:
+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.
 
 ```js
 // tsup.config.cjs
-module.exports = require('@infinitetoken/tsconfig/tsup').createTsupConfig()
+module.exports = require('@infinitetoken/tsconfig/tsup')()
 ```
 
-For a package with more than one entry point (e.g. a library plus a CLI bin), compose `entryConfig`/`cliConfig` yourself. Only the first entry should set `clean: true` — later entries with `clean: true` would wipe out what the earlier ones just wrote:
+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 })`.
 
-```js
-// tsup.config.cjs
-const { defineConfig, entryConfig, cliConfig } = require('@infinitetoken/tsconfig/tsup')
-
-module.exports = defineConfig([
-  entryConfig('src/index.ts', { clean: true }),
-  entryConfig('src/shapes.ts'),
-  cliConfig('src/cli.ts')
-])
-```
+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.
 
-`createTsupConfig(entry?, overrides?)` and `entryConfig` both default `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.
+`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.
 
 ## Release
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@infinitetoken/tsconfig",
-  "version": "0.1.4",
+  "version": "0.2.0",
   "description": "Shared base tsconfig for InfiniteToken TypeScript packages, with an opt-in tsup build config",
   "keywords": [
     "config",

package/tsup.cjs

@@ -1,61 +1,21 @@
 const { defineConfig } = require('tsup')
 
-const BASE_DEFAULTS = {
-  format: ['cjs', 'esm'],
-  dts: true
-}
-
-const CLI_DEFAULTS = {
-  format: ['esm'],
-  banner: { js: '#!/usr/bin/env node' }
-}
-
-/**
- * A single tsup build-entry object, for composing a multi-entry array yourself
- * (e.g. a library entry plus a separate subpath entry). `clean` is deliberately
- * NOT defaulted here — with multiple entries in one array, only the first should
- * clean `dist/`, or later entries wipe out earlier ones' output.
- *
- * @param {string|string[]} entry
- * @param {import('tsup').Options} [overrides]
- * @returns {import('tsup').Options}
- */
-function entryConfig(entry, overrides = {}) {
-  return {
-    entry: Array.isArray(entry) ? entry : [entry],
-    ...BASE_DEFAULTS,
-    ...overrides
-  }
-}
-
 /**
- * A CLI bin entry: ESM-only with a Node shebang banner, no declarations.
- *
- * @param {string|string[]} entry
- * @param {import('tsup').Options} [overrides]
- * @returns {import('tsup').Options}
- */
-function cliConfig(entry, overrides = {}) {
-  return {
-    entry: Array.isArray(entry) ? entry : [entry],
-    ...CLI_DEFAULTS,
-    ...overrides
-  }
-}
-
-/**
- * The common case: one library entry point, cjs+esm, with declarations and a
- * clean build. Covers most packages in the fleet outright.
- *
- * For a package with multiple entries (e.g. a CLI bin alongside the library),
- * skip this and compose `entryConfig`/`cliConfig` yourself under `defineConfig([...])`.
+ * One library entry point, cjs+esm, with declarations and a clean build.
+ * Covers the common case fleet-wide.
  *
  * @param {string|string[]} [entry]
  * @param {import('tsup').Options} [overrides]
  * @returns {import('tsup').Options}
  */
 function createTsupConfig(entry = 'src/index.ts', overrides = {}) {
-  return defineConfig(entryConfig(entry, { clean: true, ...overrides }))
+  return defineConfig({
+    entry: Array.isArray(entry) ? entry : [entry],
+    format: ['cjs', 'esm'],
+    dts: true,
+    clean: true,
+    ...overrides
+  })
 }
 
-module.exports = { createTsupConfig, entryConfig, cliConfig, defineConfig }
+module.exports = createTsupConfig