unbarrelify 1.1.0 → 1.1.2

package/README.md

@@ -16,28 +16,28 @@ export { capitalize } from "./string.ts";
 
 Barrel files are convenient, but they often come with trade-offs including:
 
-* Performance and memory: they artificially inflate the module graph and slow down startup times, HMR, and CI pipelines.
-* Tree-shaking failures: they often confuse tree-shakers, risk entire libraries to be bundled when only a single function is needed.
-* Circular dependencies: they frequently create "import cycles", crashing bundlers or causing confusing errors.
+- Performance and memory: they artificially inflate the module graph and slow down startup times, HMR, and CI pipelines.
+- Tree-shaking failures: they often confuse tree-shakers, risk entire libraries to be bundled when only a single function is needed.
+- Circular dependencies: they frequently create "import cycles", crashing bundlers or causing confusing errors.
 
 ## Resources
 
-* [Speeding up the JavaScript ecosystem - The barrel file debacle][1] (Marvin Hagemeister, 2023-10-08)
-* [How we optimized package imports in Next.js][2] (Shu Ding, 2023-10-13)
-* [A practical guide against barrel files for library authors][3] (Pascal Schilp, 2024-06-01)
-* [Please Stop Using Barrel Files][4] (Dominik Dorfmeister, 2024-07-26)
+- [Speeding up the JavaScript ecosystem - The barrel file debacle][1] (Marvin Hagemeister, 2023-10-08)
+- [How we optimized package imports in Next.js][2] (Shu Ding, 2023-10-13)
+- [A practical guide against barrel files for library authors][3] (Pascal Schilp, 2024-06-01)
+- [Please Stop Using Barrel Files][4] (Dominik Dorfmeister, 2024-07-26)
 
 ## Features
 
-* Automated rewiring of consumers to import directly from source
-* Preserves path aliases
-* Skips barrel files that are entry points (`package.json#exports` etc.)
-* Auto-detects or enforces file extensions to match project style
-* Optional `--organize-imports` to dedupe and clean up after rewrites
-* Granular control with `--skip`, `--only` or add `--barrel`-like files
-* Use `--check` for CI to fail if barrel files are detected
-* Go all out with `--unsafe-namespace` to namespace imports (warning: naive)
-* [Verified on non-trivial repositories][5] to not break the build/tests
+- Automated rewiring of consumers to import directly from source
+- Preserves path aliases
+- Skips barrel files that are entry points (`package.json#exports` etc.)
+- Auto-detects or enforces file extensions to match project style
+- Optional `--organize-imports` to dedupe and clean up after rewrites
+- Granular control with `--skip`, `--only` or add `--barrel`-like files
+- Use `--check` for CI to fail if barrel files are detected
+- Go all out with `--unsafe-namespace` to namespace imports (warning: naive)
+- [Verified on non-trivial repositories][5] to not break the build/tests
 
 ## Usage
 
@@ -139,7 +139,7 @@ interface Result {
   preserved: PreservedBarrel[];
 }
 
- interface PreservedBarrel {
+interface PreservedBarrel {
   path: string;
   reason: "skip" | "namespace-import" | "non-ts-import" | "dynamic-import";
   consumers: string[];
@@ -174,16 +174,25 @@ import { formatDate } from "./utils/date.ts";
 import { capitalize } from "./utils/string.ts";
 ```
 
+## Preserved barrel files
+
+This prevents barrel files from getting deleted:
+
+- File is in `package.json` such as `main` or `exports` field.
+- File is `index.*` at root level (of each workspace).
+- File is in `--skip` argument.
+- Dynamic import calls are not modified, so the imported barrel file is not deleted (e.g. `import("barrel.ts")`).
+- Non-JS/TS files are not modified, so the imported barrel file is not deleted (e.g. `*.mdx`).
+- Namespace imports are not modified, use `--unsafe-namespace` to rewrite (e.g. `import * as NS from "barrel"`).
+
+The output in CLI prints "Preserved barrel files" with details.
+
 ## License
 
 ISC
 
 [1]: https://marvinh.dev/blog/speeding-up-javascript-ecosystem-part-7/
-
 [2]: https://vercel.com/blog/how-we-optimized-package-imports-in-next-js
-
 [3]: https://dev.to/thepassle/a-practical-guide-against-barrel-files-for-library-authors-118c
-
 [4]: https://tkdodo.eu/blog/please-stop-using-barrel-files
-
 [5]: https://github.com/webpro/unbarrelify/blob/main/.github/workflows/integration.yml

package/package.json

@@ -1,8 +1,31 @@
 {
   "name": "unbarrelify",
-  "version": "1.1.0",
-  "type": "module",
+  "version": "1.1.2",
   "description": "Barrel file removal tool for JavaScript & TypeScript projects (ESM-only)",
+  "keywords": [
+    "ESM",
+    "barrel",
+    "codemod",
+    "exports",
+    "files",
+    "imports",
+    "index",
+    "refactor",
+    "rewrite",
+    "typescript"
+  ],
+  "license": "ISC",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/webpro-nl/unbarrelify.git"
+  },
+  "bin": {
+    "unbarrelify": "./dist/cli.js"
+  },
+  "files": [
+    "dist"
+  ],
+  "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
   "exports": {
@@ -11,40 +34,25 @@
       "import": "./dist/index.js"
     }
   },
-  "bin": {
-    "unbarrelify": "./dist/cli.js"
-  },
-  "files": [
-    "dist"
-  ],
   "scripts": {
     "build": "tsc",
     "test": "node --test test/**/*.test.ts",
+    "lint": "oxlint",
+    "format": "oxfmt",
     "prepack": "tsc"
   },
   "dependencies": {
-    "oxc-resolver": "^11.16.3",
-    "tinyglobby": "^0.2.15",
-    "typescript": "^5.9.3"
+    "oxc-resolver": "^11.19.1",
+    "tinyglobby": "^0.2.16",
+    "typescript": "^6.0.3"
   },
   "devDependencies": {
-    "@types/node": "^24.10.9"
+    "@types/node": "^24.10.9",
+    "oxfmt": "^0.50.0",
+    "oxlint": "^1.65.0"
   },
   "engines": {
     "node": ">=20.12.0"
   },
-  "keywords": [
-    "barrel",
-    "codemod",
-    "ESM",
-    "exports",
-    "files",
-    "imports",
-    "index",
-    "refactor",
-    "rewrite",
-    "typescript"
-  ],
-  "license": "ISC",
-  "packageManager": "pnpm@10.28.1"
+  "packageManager": "pnpm@11.1.3"
 }