@webpieces/code-rules 0.4.574 → 0.4.575

package/package.json

@@ -1,13 +1,9 @@
 {
   "name": "@webpieces/code-rules",
-  "version": "0.4.574",
+  "version": "0.4.575",
   "description": "Standalone code validation rules extracted from architecture-validators, no Nx dependency required",
   "type": "commonjs",
   "main": "./src/index.js",
-  "bin": {
-    "wp-validate-code": "./bin/wp-validate-code.js",
-    "wp-ci": "./bin/wp-ci.js"
-  },
   "files": [
     "src/**/*",
     "bin/**/*"
@@ -20,12 +16,16 @@
     "directory": "packages/tooling/code-rules"
   },
   "dependencies": {
-    "@webpieces/rules-config": "0.4.574",
+    "@webpieces/rules-config": "0.4.575",
     "@inversifyjs/binding-decorators": "1.1.5",
     "inversify": "7.10.4",
     "reflect-metadata": "0.2.2"
   },
   "publishConfig": {
+    "bin": {
+      "wp-validate-code": "./src/cli.js",
+      "wp-ci": "./src/wp-ci.js"
+    },
     "access": "public"
   },
   "types": "./src/index.d.ts"

package/bin/wp-ci.js

@@ -1,27 +0,0 @@
-#!/usr/bin/env node
-// Plain JS shim -> delegates to the compiled TypeScript entry point.
-//
-// Must NOT be converted to TypeScript. pnpm chmods every `bin` target while it links a
-// package, and in THIS workspace a `workspace:*` sibling is linked from its SOURCE dir,
-// long before any build has produced `src/wp-ci.js`. Pointing `bin` straight at the
-// compiled path therefore makes every `pnpm install` print
-// `WARN Failed to create bin ... ENOENT ... chmod` — noise indistinguishable from a real
-// bin-link failure. This file exists in git, so the chmod always succeeds.
-//
-// See setupDebugging.md (Attempt 8) and bin-targets-exist.spec.ts, which fails if any
-// `bin` target in the workspace does not exist on disk.
-'use strict';
-
-const path = require('path');
-const fs = require('fs');
-
-const compiled = path.join(__dirname, '..', 'src', 'wp-ci.js');
-
-if (!fs.existsSync(compiled)) {
-    console.error(
-        '  [code-rules] wp-ci: package not built yet. Run the build first, or install from npm.',
-    );
-    process.exit(1);
-}
-
-require(compiled);

package/bin/wp-validate-code.js

@@ -1,27 +0,0 @@
-#!/usr/bin/env node
-// Plain JS shim -> delegates to the compiled TypeScript entry point.
-//
-// Must NOT be converted to TypeScript. pnpm chmods every `bin` target while it links a
-// package, and in THIS workspace a `workspace:*` sibling is linked from its SOURCE dir,
-// long before any build has produced `src/cli.js`. Pointing `bin` straight at the
-// compiled path therefore makes every `pnpm install` print
-// `WARN Failed to create bin ... ENOENT ... chmod` — noise indistinguishable from a real
-// bin-link failure. This file exists in git, so the chmod always succeeds.
-//
-// See setupDebugging.md (Attempt 8) and bin-targets-exist.spec.ts, which fails if any
-// `bin` target in the workspace does not exist on disk.
-'use strict';
-
-const path = require('path');
-const fs = require('fs');
-
-const compiled = path.join(__dirname, '..', 'src', 'cli.js');
-
-if (!fs.existsSync(compiled)) {
-    console.error(
-        '  [code-rules] wp-validate-code: package not built yet. Run the build first, or install from npm.',
-    );
-    process.exit(1);
-}
-
-require(compiled);