@chipmobilesdk/rn-i18n-tooling 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,4 +1,29 @@
-# @chipmobilesdk/rn-i18n-tooling
+# @chipmobilesdk/rn-i18n-tooling
+
+## 0.1.1
+
+### Patch Changes
+
+- `chip-i18n` runs on Linux and macOS again. ([#27](https://github.com/operationd8979/chip-mobile-sdk/pull/27))
+
+  Every line of `bin/chip-i18n.mjs` in 0.1.0 ends in CRLF, the shebang included, so the
+  kernel reads the interpreter name as `node\r` and the command dies before it starts:
+
+  ```
+  $ npx chip-i18n --help
+  /usr/bin/env: 'node\r': No such file or directory
+  ```
+
+  Only away from Windows. 0.1.0 had to be published by hand — npm's trusted publishing
+  cannot create a package that does not exist yet — and `npm pack` ships the working tree
+  as it stands, which on a Windows checkout (`core.autocrlf`) had every line rewritten. The
+  package's own smoke test installs the tarball and runs the binary, but it passes on
+  Windows, where CRLF is fine, and in CI, where the checkout is LF: the broken artifact
+  exists only in between.
+
+  `.gitattributes` now pins `packages/*/bin/**` to LF so no checkout can rewrite it, and
+  `npm run check:manifests` fails on a `bin` target that contains a carriage return or is
+  missing its shebang. Nothing else in the package changed.
 
 ## 0.1.0
 

package/README.md

@@ -1,65 +1,65 @@
-# @chipmobilesdk/rn-i18n-tooling
-
-The `chip-i18n` CLI: it scans a React Native app's source for translation keys and
-synchronises the app's locale JSON files against what it finds.
-
-- **Node, not React Native.** Nothing here runs on a device, and the package is a
-  `devDependency` of the app. The runtime library is
-  [`@chipmobilesdk/rn-i18n`](../rn-i18n/README.md).
-- **Ships JavaScript.** The tarball carries `lib/` built from TypeScript plus the
-  `bin/chip-i18n.mjs` entry. This package exists because the tooling used to ship as
-  `.ts` source inside the runtime tarball, where the documented command — `node
-  --experimental-strip-types node_modules/@chipmobilesdk/rn-i18n/src/tooling/cli.ts` —
-  worked in this monorepo and nowhere else (I18N-01, DEP-02).
-- **Public package.** Published under the `@chipmobilesdk` npm organization. The
-  license is `UNLICENSED`: the code is readable on npm, but
-  no open-source license is granted.
-- **Version**: see [CHANGELOG](CHANGELOG.md)
-
-## Install
-
-```sh
-npm i -D @chipmobilesdk/rn-i18n-tooling
-```
-
-Node `>=22.13.0`.
-
-## Use
-
-```sh
-npx chip-i18n sync                              # i18n-sync.config.json
-npx chip-i18n sync --config other.config.json
-npx chip-i18n --help
-```
-
-The configuration file, the key patterns, the runtime-only key policy and the generated
-typed-key contract are documented in the runtime package's README, under
-`## Extraction & synchronization CLI` — the CLI reads the same config it always did.
-
-Exit codes: `0` success or warnings, `1` blocking findings (a key with two different
-default texts, a malformed locale file), `2` invalid configuration or usage.
-
-A run that finds nothing to change **writes no file**: each locale file is compared
-with what would be written and left alone when it matches. That makes the command safe
-in a watch loop or a pre-commit hook, where rewriting identical bytes used to churn
-mtimes and show work in `git status` that had not happened.
-
-## Programmatic use
-
-The same functions are importable, for a repository that wants to drive extraction from
-its own script:
-
-```ts
-import { runSync, renderReport, scanSource } from '@chipmobilesdk/rn-i18n-tooling';
-```
-
-`runSync(rootDir, config)` returns the report and whether the generated keys file
-changed; `scanSource` is the scanner on its own. Both are the ones the CLI uses.
-
-## Repository layout
-
-| | |
-|---|---|
-| `src/` | TypeScript sources; `cli.ts` is the command |
-| `lib/` | build output (`npm run build`), git-ignored, published |
-| `bin/chip-i18n.mjs` | the published binary, a wrapper over `lib/cli.js` |
+# @chipmobilesdk/rn-i18n-tooling
+
+The `chip-i18n` CLI: it scans a React Native app's source for translation keys and
+synchronises the app's locale JSON files against what it finds.
+
+- **Node, not React Native.** Nothing here runs on a device, and the package is a
+  `devDependency` of the app. The runtime library is
+  [`@chipmobilesdk/rn-i18n`](../rn-i18n/README.md).
+- **Ships JavaScript.** The tarball carries `lib/` built from TypeScript plus the
+  `bin/chip-i18n.mjs` entry. This package exists because the tooling used to ship as
+  `.ts` source inside the runtime tarball, where the documented command — `node
+  --experimental-strip-types node_modules/@chipmobilesdk/rn-i18n/src/tooling/cli.ts` —
+  worked in this monorepo and nowhere else (I18N-01, DEP-02).
+- **Public package.** Published under the `@chipmobilesdk` npm organization. The
+  license is `UNLICENSED`: the code is readable on npm, but
+  no open-source license is granted.
+- **Version**: see [CHANGELOG](CHANGELOG.md)
+
+## Install
+
+```sh
+npm i -D @chipmobilesdk/rn-i18n-tooling
+```
+
+Node `>=22.13.0`.
+
+## Use
+
+```sh
+npx chip-i18n sync                              # i18n-sync.config.json
+npx chip-i18n sync --config other.config.json
+npx chip-i18n --help
+```
+
+The configuration file, the key patterns, the runtime-only key policy and the generated
+typed-key contract are documented in the runtime package's README, under
+`## Extraction & synchronization CLI` — the CLI reads the same config it always did.
+
+Exit codes: `0` success or warnings, `1` blocking findings (a key with two different
+default texts, a malformed locale file), `2` invalid configuration or usage.
+
+A run that finds nothing to change **writes no file**: each locale file is compared
+with what would be written and left alone when it matches. That makes the command safe
+in a watch loop or a pre-commit hook, where rewriting identical bytes used to churn
+mtimes and show work in `git status` that had not happened.
+
+## Programmatic use
+
+The same functions are importable, for a repository that wants to drive extraction from
+its own script:
+
+```ts
+import { runSync, renderReport, scanSource } from '@chipmobilesdk/rn-i18n-tooling';
+```
+
+`runSync(rootDir, config)` returns the report and whether the generated keys file
+changed; `scanSource` is the scanner on its own. Both are the ones the CLI uses.
+
+## Repository layout
+
+| | |
+|---|---|
+| `src/` | TypeScript sources; `cli.ts` is the command |
+| `lib/` | build output (`npm run build`), git-ignored, published |
+| `bin/chip-i18n.mjs` | the published binary, a wrapper over `lib/cli.js` |

package/bin/chip-i18n.mjs

@@ -1,17 +1,17 @@
-#!/usr/bin/env node
-// The published entry point for `npx chip-i18n`. It is a hand-written wrapper
-// rather than the built `lib/cli.js` directly: a shebang in a TypeScript source
-// file is at the mercy of the emitter, and this file is also where the error for
-// "installed but never built" belongs.
-import { existsSync } from 'node:fs';
-import { fileURLToPath } from 'node:url';
-
-const cli = new URL('../lib/cli.js', import.meta.url);
-if (!existsSync(fileURLToPath(cli))) {
-	console.error(
-		'[chip-i18n] This package was installed without its build output. Reinstall it from npm, or run `npm run build` in packages/rn-i18n-tooling.',
-	);
-	process.exitCode = 2;
-} else {
-	await import(cli.href);
-}
+#!/usr/bin/env node
+// The published entry point for `npx chip-i18n`. It is a hand-written wrapper
+// rather than the built `lib/cli.js` directly: a shebang in a TypeScript source
+// file is at the mercy of the emitter, and this file is also where the error for
+// "installed but never built" belongs.
+import { existsSync } from 'node:fs';
+import { fileURLToPath } from 'node:url';
+
+const cli = new URL('../lib/cli.js', import.meta.url);
+if (!existsSync(fileURLToPath(cli))) {
+	console.error(
+		'[chip-i18n] This package was installed without its build output. Reinstall it from npm, or run `npm run build` in packages/rn-i18n-tooling.',
+	);
+	process.exitCode = 2;
+} else {
+	await import(cli.href);
+}

package/lib/cli.js

@@ -13,10 +13,10 @@ import path from 'node:path';
 import process from 'node:process';
 import { renderReport } from "./report.js";
 import { SyncConfigError, runSync } from "./runner.js";
-const USAGE = `Usage: chip-i18n sync [--config <path>]
-
-  sync   Scan the configured source globs, update the locale files and report.
-         --config defaults to i18n-sync.config.json, resolved from the current
+const USAGE = `Usage: chip-i18n sync [--config <path>]
+
+  sync   Scan the configured source globs, update the locale files and report.
+         --config defaults to i18n-sync.config.json, resolved from the current
          working directory.`;
 export function parseArgs(argv) {
     let configPath = 'i18n-sync.config.json';

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@chipmobilesdk/rn-i18n-tooling",
-	"version": "0.1.0",
+	"version": "0.1.1",
 	"private": false,
 	"license": "UNLICENSED",
 	"description": "The chip-i18n CLI: extracts translation keys from a React Native app's source and synchronises its locale files.",