@kitschpatrol/shared-config 5.0.7 → 5.1.0

package/bin/cli.js

@@ -6569,6 +6569,7 @@ var source_default = chalk;
 
 // ../../src/command-builder.ts
 import { cosmiconfig } from "cosmiconfig";
+import { TypeScriptLoader as typeScriptLoader } from "cosmiconfig-typescript-loader";
 import { execa } from "execa";
 import fse2 from "fs-extra";
 import fs3 from "node:fs";
@@ -11493,7 +11494,7 @@ var Yargs = YargsFactory(esm_default);
 var yargs_default = Yargs;
 
 // ../../package.json
-var version = "5.0.7";
+var version = "5.1.0";
 
 // ../../src/execa-utilities.ts
 function isErrorExecaError(error) {
@@ -11834,11 +11835,11 @@ async function executeCliCommand(logStream, positionalArguments, optionFlags, co
       env: {
         // Use colorful output unless NO_COLOR is set
         // eslint-disable-next-line ts/naming-convention
-        ...process.env.NO_COLOR === void 0 ? { FORCE_COLOR: "true" } : {},
-        // Quiet node for when processing *.config.ts files in Node 22
+        ...process.env.NO_COLOR === void 0 ? { FORCE_COLOR: "true" } : {}
+        // Quiet Node when processing *.config.ts files in Node 22
         // Suppress experimental type stripping warning with --no-warnings
-        // eslint-disable-next-line ts/naming-convention
-        NODE_OPTIONS: "--experimental-strip-types --disable-warning=ExperimentalWarning"
+        // TODO what's the story here on Node 20?
+        // NODE_OPTIONS: '--experimental-strip-types --disable-warning=ExperimentalWarning',
       },
       preferLocal: true,
       reject: false,
@@ -12161,6 +12162,14 @@ function getCosmiconfigCommand(configName) {
 }
 async function getCosmiconfigResult(configName) {
   const explorer = cosmiconfig(configName, {
+    loaders: {
+      // Using the alternate typescript loader fixes ERR_MODULE_NOT_FOUND errors
+      // in configuration files that import modules via a path
+      // https://github.com/cosmiconfig/cosmiconfig/issues/345
+      // https://github.com/Codex-/cosmiconfig-typescript-loader
+      // Same approach taken in mdat's implementation...
+      ".ts": typeScriptLoader()
+    },
     searchStrategy: "project"
     // Alt approach?
     // searchStrategy: 'global',
@@ -12451,13 +12460,13 @@ var sharedKnipConfig = {
     "src/{index,cli,main}.{js,mjs,cjs,jsx,ts,tsx,mts,cts}!",
     // Customized entries
     "src/{bin,lib,cli}/{index,cli,main}.{js,mjs,cjs,jsx,ts,tsx,mts,cts}!",
-    "scripts/**/*.ts",
-    ".remarkrc.js",
-    "cspell.config.js",
-    "eslint.config.ts",
-    "mdat.config.ts",
-    "prettier.config.js",
-    "stylelint.config.js"
+    "scripts/**/*.{js,mjs,cjs,ts,mts,cts}",
+    ".remarkrc.{js,mjs,cjs,ts,mts,cts}",
+    "cspell.config.{js,mjs,cjs,ts,mts,cts}",
+    "eslint.config.{js,mjs,cjs,ts,mts,cts}",
+    "mdat.config.{js,mjs,cjs,ts,mts,cts}",
+    "prettier.config.{js,mjs,cjs,ts,mts,cts}",
+    "stylelint.config.{js,mjs,cjs,ts,mts,cts}"
   ],
   // Allow calling of individual kpi binaries...
   ignoreBinaries: [
@@ -13274,15 +13283,12 @@ function updateLicenseContent(content, currentYear) {
 async function copyrightYear(logStream, fix = false) {
   const currentYear = (/* @__PURE__ */ new Date()).getFullYear();
   const licenseFiles = [];
-  const patterns = [
-    "**/license.txt",
-    "**/LICENSE.txt",
-    "**/License.txt",
-    "**/LICENSE",
-    "!node_modules/**"
-  ];
+  const patterns = ["**/license.txt", "**/license", "!node_modules/**"];
   const files = await globby(patterns, {
+    caseSensitiveMatch: false,
     cwd: getPackageDirectory(),
+    followSymbolicLinks: false,
+    // Avoid infinite loops
     gitignore: true
   });
   for (const filePath of files) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kitschpatrol/shared-config",
-  "version": "5.0.7",
+  "version": "5.1.0",
   "description": "A collection of shared configurations, linters, and formatting tools for TypeScript projects. All managed as a single dependency, and invoked via a single CLI command.",
   "keywords": [
     "shared-config",
@@ -38,19 +38,20 @@
   "dependencies": {
     "@pinojs/json-colorizer": "^4.0.0",
     "cosmiconfig": "^9.0.0",
+    "cosmiconfig-typescript-loader": "^6.1.0",
     "execa": "^9.5.2",
     "find-workspaces": "^0.3.1",
     "fs-extra": "^11.3.0",
-    "prettier": "^3.5.2",
-    "@kitschpatrol/cspell-config": "5.0.7",
-    "@kitschpatrol/eslint-config": "5.0.7",
-    "@kitschpatrol/knip-config": "5.0.7",
-    "@kitschpatrol/remark-config": "5.0.7",
-    "@kitschpatrol/prettier-config": "5.0.7",
-    "@kitschpatrol/typescript-config": "5.0.7",
-    "@kitschpatrol/mdat-config": "5.0.7",
-    "@kitschpatrol/repo-config": "5.0.7",
-    "@kitschpatrol/stylelint-config": "5.0.7"
+    "prettier": "^3.5.3",
+    "@kitschpatrol/cspell-config": "5.1.0",
+    "@kitschpatrol/prettier-config": "5.1.0",
+    "@kitschpatrol/eslint-config": "5.1.0",
+    "@kitschpatrol/knip-config": "5.1.0",
+    "@kitschpatrol/remark-config": "5.1.0",
+    "@kitschpatrol/mdat-config": "5.1.0",
+    "@kitschpatrol/repo-config": "5.1.0",
+    "@kitschpatrol/stylelint-config": "5.1.0",
+    "@kitschpatrol/typescript-config": "5.1.0"
   },
   "devDependencies": {
     "chalk": "^5.4.1",

package/readme.md

@@ -126,17 +126,19 @@ The top-level `kpi` command also takes care of some nuances in terms of _which_
 Bootstrap a new project and open in VS Code:
 
 ```sh
-git init && pnpm init && pnpm pkg set type="module" && pnpm dlx @kitschpatrol/repo-config init && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init --location package && pnpm i && code .
+git init && pnpm init && pnpm pkg set type="module" && pnpm dlx @kitschpatrol/repo-config init && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init && pnpm i && code .
 ```
 
-The `--location package` flag will put as much configuration in your `package.json` as possible instead of in discrete files in your project root. This saves some clutter but can make it clunkier to extend or customize configurations. At any point, you can call `kpi init` with or without a `--location package` or `--location file` flag to reinitialize your configuration files in one place or the other.
+Note that `kpi init` takes an optional `--location package` flag will put as much configuration in your `package.json` as possible instead of creating discrete config files in your project root for each tool. Putting config in `package.json` can save some clutter, but can make it clunkier to extend or customize configurations.
+
+At any point, you can call `kpi init` again with the `--location package` or `--location file` flag to reinitialize your configuration files in one place or the other and restore the default configurations.
 
 #### Quick add to an existing project:
 
 This might overwrite certain config files, so commit first:
 
 ```sh
-pnpm dlx @kitschpatrol/repo-config init && pnpm i && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init --location package
+pnpm dlx @kitschpatrol/repo-config init && pnpm i && pnpm add -D @kitschpatrol/shared-config && pnpm kpi init
 ```
 
 #### Step-by-step: