next-intl-codemod 0.1.0 → 0.1.1

package/README.md

@@ -56,6 +56,14 @@ t.rich('Please accept the <link>terms</link>.', {link: (chunks) => <a>{chunks}</
 | `--dry-run` | | Report only |
 | `--report <file>` | | JSON report: skipped bindings with reasons, conflicts, old keys never referenced, and `keyMap` (old key → new id) |
 
+## Requirements
+
+The `po` format needs **next-intl 4.14.0 or newer**. That release changed the PO layout, and older
+extractors erase the translations of a catalog in the new layout on the next `next dev` or
+`next build`, so the codemod stops if it finds an older version. In a monorepo, upgrade every
+workspace package to the same version and migrate any other PO catalog that next-intl loads, such as
+a shared package's. The codemod only checks the catalogs in `--out`.
+
 ## Choosing the source locale
 
 Inline messages are written in one locale and that locale must be the `messages.sourceLocale` of

package/dist/apply.js

@@ -24,6 +24,29 @@ export function applyEdits(edits, textByFile) {
         fs.writeFileSync(file, bom + text);
     }
 }
+/**
+ * next-intl 4.14.0 moved PO catalogs to the source text in `msgid` and the key in `msgctxt`. An older
+ * extractor reads that layout as namespace + key and rewrites the catalogs with every translation empty.
+ */
+export function assertNextIntlSupportsPo(options) {
+    if (options.format !== 'po')
+        return;
+    for (let dir = options.projectRoot;; dir = path.dirname(dir)) {
+        const file = path.join(dir, 'node_modules/next-intl/package.json');
+        if (fs.existsSync(file)) {
+            const { version } = JSON.parse(fs.readFileSync(file, 'utf8'));
+            const [major, minor] = version.split('.').map(Number);
+            if (major < 4 || (major === 4 && minor < 14)) {
+                throw new Error(`next-intl ${version} is installed, but PO catalogs written by this codemod need next-intl 4.14.0 or newer: ` +
+                    'older extractors erase their translations on the next `next dev` or `next build`. ' +
+                    'Upgrade next-intl (including workspace packages) or use --format json. Nothing was changed.');
+            }
+            return;
+        }
+        if (dir === path.dirname(dir))
+            return;
+    }
+}
 /** Merging into the previous layout would write a catalog next-intl refuses to read. */
 export function assertCatalogsSupported(options) {
     if (options.format !== 'po')

package/dist/cli.js

@@ -2,7 +2,7 @@
 import fs from 'node:fs';
 import path from 'node:path';
 import { parseArgs } from 'node:util';
-import { applyEdits, assertCatalogsSupported, writeCatalogs } from './apply.js';
+import { applyEdits, assertCatalogsSupported, assertNextIntlSupportsPo, writeCatalogs } from './apply.js';
 import { loadCatalogs } from './catalog.js';
 import { collectSourceFiles } from './files.js';
 import { buildPlan } from './plan.js';
@@ -47,6 +47,7 @@ if (!['po', 'json'].includes(format))
     throw new Error(`Unknown format: ${format}`);
 if (!['none', 'first-segment', 'keep'].includes(namespace))
     throw new Error(`Unknown namespace strategy: ${namespace}`);
+assertNextIntlSupportsPo({ projectRoot, format });
 const catalogs = loadCatalogs(values.messages, projectRoot, values['source-locale']);
 assertCatalogsSupported({ outDir: path.resolve(projectRoot, values.out), format, locales: catalogs.locales });
 const files = [];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "next-intl-codemod",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "bin": {
     "next-intl-codemod": "dist/cli.js"