babel-plugin-saykit 0.8.0 → 0.9.0

package/dist/{catalogue-B3HA3aVz.cjs → catalogue-CrZhNHS_.cjs}

@@ -2,30 +2,9 @@ let node_path = require("node:path");
 let node_fs = require("node:fs");
 let _saykit_config_features_catalogue = require("@saykit/config/features/catalogue");
 //#region src/catalogue.ts
-/** Normalise an absolute path into the form bucket globs are written against. */
 const toId = (path) => (0, node_path.relative)(process.cwd(), path).replaceAll("\\", "/").split("?")[0];
-/**
-* The glob a bucket's catalogues match, e.g. `src/locales/*.po` — the `output`
-* template with its placeholders filled in. Bundlers that select files by glob
-* rather than by predicate need this to target exactly the catalogues, and
-* nothing else sharing their extension.
-*/
 const catalogueGlob = (bucket) => String(bucket.output).replace("{locale}", "*").replace("{extension}", bucket.formatter.extension.slice(1)).replaceAll("\\", "/").replace(/^\.\//, "");
-/** Whether `path` is one of the config's catalogue outputs. */
 const isCatalogue = (config, path) => config.buckets.some((bucket) => bucket.output.match(toId(path)));
-/**
-* Assemble the catalogue at `path` into a `{ id: string }` record, merging in
-* the fallback chain (configured fallbacks + the source locale) so an
-* untranslated key resolves to a fallback string rather than going missing.
-*
-* Returns `undefined` when the path is not a catalogue, and otherwise reports
-* the files that fed the record alongside it — a bundler that can track them
-* gets invalidation for free when a fallback locale is edited.
-*
-* Reads are synchronous so every caller can share one implementation: Babel's
-* visitor cannot await, and the handful of files in a fallback chain are not
-* worth an async path in a bundler that is blocked on the result anyway.
-*/
 function loadCatalogue(config, path) {
 	const id = toId(path);
 	const bucket = config.buckets.find((b) => b.output.match(id));

package/dist/index.cjs

@@ -1,9 +1,8 @@
-const require_catalogue = require("./catalogue-B3HA3aVz.cjs");
+const require_catalogue = require("./catalogue-CrZhNHS_.cjs");
 let node_path = require("node:path");
-let _babel_core = require("@babel/core");
 let _saykit_config_features_loader = require("@saykit/config/features/loader");
 //#region src/index.ts
-var src_default = (_, { catalogues = "inline" } = {}) => {
+var src_default = ({ types: t }, { catalogues = "inline" } = {}) => {
 	const config = (0, _saykit_config_features_loader.resolveConfig)();
 	return {
 		name: "saykit",
@@ -16,7 +15,7 @@ var src_default = (_, { catalogues = "inline" } = {}) => {
 			if (!catalogue) return;
 			const [specifier, ...rest] = path.node.specifiers;
 			if (specifier?.type !== "ImportDefaultSpecifier" || rest.length > 0) throw path.buildCodeFrameError("SayKit inline imports require a single default import");
-			path.replaceWith(_babel_core.types.variableDeclaration("const", [_babel_core.types.variableDeclarator(_babel_core.types.identifier(specifier.local.name), _babel_core.types.objectExpression(Object.entries(catalogue.record).map(([key, value]) => _babel_core.types.objectProperty(_babel_core.types.stringLiteral(key), _babel_core.types.stringLiteral(value)))))]));
+			path.replaceWith(t.variableDeclaration("const", [t.variableDeclarator(t.identifier(specifier.local.name), t.objectExpression(Object.entries(catalogue.record).map(([key, value]) => t.objectProperty(t.stringLiteral(key), t.stringLiteral(value)))))]));
 		} },
 		parserOverride(code, opts, parse) {
 			const id_ = opts.sourceFileName;

package/dist/index.d.cts

@@ -1,4 +1,4 @@
-import { PluginObj, parse } from "@babel/core";
+import { ConfigAPI, PluginObj, parse, types } from "@babel/core";
 //#region src/index.d.ts
 declare module '@babel/core' {
   interface PluginObj {
@@ -21,6 +21,8 @@ interface Options {
    */
   catalogues?: 'inline' | 'module';
 }
-declare const _default: (_: unknown, { catalogues }?: Options) => PluginObj;
+declare const _default: ({ types: t }: ConfigAPI & {
+  types: typeof types;
+}, { catalogues }?: Options) => PluginObj;
 //#endregion
 export { Options, _default as default };

package/dist/metro/index.cjs

@@ -3,13 +3,6 @@ let node_path = require("node:path");
 let _saykit_config_features_loader = require("@saykit/config/features/loader");
 let node_module = require("node:module");
 //#region src/metro/index.ts
-/**
-* Resolve Metro's own transformer from the project rather than from this
-* package, since it is the project that depends on Metro.
-*
-* The base is the config's `projectRoot` — `process.cwd()` is wrong whenever
-* Metro is started from elsewhere, which in a monorepo is the normal case.
-*/
 const transformerPath = (0, node_path.join)(__dirname, "transformer.cjs");
 function resolveUpstream(specifier, projectRoot) {
 	if ((0, node_path.isAbsolute)(specifier)) return specifier;
@@ -19,21 +12,6 @@ function resolveUpstream(specifier, projectRoot) {
 		return require.resolve(specifier);
 	}
 }
-/**
-* Wrap a Metro config so SayKit catalogues load as real modules.
-*
-* ```js
-* const { withSayKit } = require('babel-plugin-saykit/metro');
-* module.exports = withSayKit(getDefaultConfig(__dirname));
-* ```
-*
-* Metro's transform cache is keyed on each file's own bytes, so a catalogue has
-* to stay a module of its own to be invalidated at all — see
-* `./transformer.ts`.
-*
-* Apply this outermost. Anything wrapped around it that also sets
-* `transformerPath` replaces this one, and catalogues stop being assembled.
-*/
 function withSayKit(metroConfig) {
 	if (metroConfig.transformerPath === transformerPath) return metroConfig;
 	const extensions = (0, _saykit_config_features_loader.resolveConfig)().buckets.map((bucket) => bucket.formatter.extension.slice(1)).filter((extension) => extension !== "json");

package/dist/metro/transformer.cjs

@@ -1,5 +1,5 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_catalogue = require("../catalogue-B3HA3aVz.cjs");
+const require_catalogue = require("../catalogue-CrZhNHS_.cjs");
 let node_path = require("node:path");
 let _saykit_config_features_loader = require("@saykit/config/features/loader");
 let node_fs = require("node:fs");
@@ -7,21 +7,7 @@ let node_crypto = require("node:crypto");
 //#region src/metro/transformer.ts
 const config = (0, _saykit_config_features_loader.resolveConfig)();
 const upstream = (transformerConfig) => require(transformerConfig.saykitTransformerPath);
-/**
-* What a catalogue transforms into depends on the SayKit config — the fallback
-* chain it resolves, the formatter that parses it — and on the version of this
-* package doing the assembling. Neither is a byte of the file Metro hashes, so
-* without them in the cache key, editing `saykit.config.*` or upgrading leaves
-* every catalogue serving the record it was cached with.
-*/
 const salt = (0, node_crypto.createHash)("sha1").update((0, node_fs.readFileSync)((0, node_path.join)(__dirname, "..", "..", "package.json"), "utf8")).update((0, node_fs.readFileSync)((0, _saykit_config_features_loader.resolveConfigFile)(), "utf8")).digest("hex");
-/**
-* Metro reads `.json` straight through `transformJSON` and never runs Babel over
-* it, so a Babel plugin cannot reach a catalogue at all. Wrapping the transform
-* worker is the one place that can: it substitutes the assembled record for the
-* catalogue's own source, leaving the file a real module whose sha1 — and
-* therefore Metro's transform cache entry — moves whenever it is edited.
-*/
 function transform(transformerConfig, projectRoot, filename, data, options) {
 	const worker = upstream(transformerConfig);
 	const catalogue = require_catalogue.loadCatalogue(config, filename);

package/dist/next/index.cjs

@@ -1,24 +1,8 @@
 Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-const require_catalogue = require("../catalogue-B3HA3aVz.cjs");
+const require_catalogue = require("../catalogue-CrZhNHS_.cjs");
 let _saykit_config_features_loader = require("@saykit/config/features/loader");
 //#region src/next/index.ts
 const loader = "babel-plugin-saykit/next/loader";
-/**
-* Wrap a Next config so SayKit catalogues load as real modules.
-*
-* ```js
-* import { withSayKit } from 'babel-plugin-saykit/next';
-* export default withSayKit({});
-* ```
-*
-* Pair it with `catalogues: 'module'` on the Babel plugin — the plugin has to
-* leave the import alone for the loader to ever be asked for the module.
-*
-* Rules are derived from the SayKit config, so both bundlers get one per bucket
-* targeting exactly that bucket's `output` — nothing else sharing the extension
-* goes through the loader, which matters most for a `.json` bucket, where the
-* alternative would be routing every JSON import in the app through it.
-*/
 function withSayKit(nextConfig = {}) {
 	const config = (0, _saykit_config_features_loader.resolveConfig)();
 	const rules = Object.fromEntries(config.buckets.map((bucket) => [`**/${require_catalogue.catalogueGlob(bucket)}`, {

package/dist/next/loader.cjs

@@ -1,20 +1,6 @@
-const require_catalogue = require("../catalogue-B3HA3aVz.cjs");
+const require_catalogue = require("../catalogue-CrZhNHS_.cjs");
 //#region src/next/loader.ts
 const config = (0, require("@saykit/config/features/loader").resolveConfig)();
-/**
-* Replaces a catalogue file with its assembled record.
-*
-* This is a *loader* rather than a plugin because Turbopack runs loaders and
-* not webpack plugins, and it is published only so `withSayKit` can name it in
-* the rules it generates. A plain webpack, Vite or Rollup build should reach for
-* `unplugin-saykit` instead, which does the same job through each bundler's own
-* plugin API.
-*
-* The catalogue stays a real module, which is the whole point: the importer
-* keeps a dependency edge to it, so editing a catalogue invalidates exactly the
-* modules that read it. Inlining the record into the importer instead leaves the
-* importer's own bytes unchanged, and no bundler can invalidate on that.
-*/
 function saykitLoader(source) {
 	const catalogue = require_catalogue.loadCatalogue(config, this.resourcePath);
 	if (!catalogue) return source;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "babel-plugin-saykit",
-  "version": "0.8.0",
+  "version": "0.9.0",
   "description": "Babel plugin for SayKit",
   "keywords": [
     "i18n",
@@ -48,12 +48,15 @@
     "provenance": true
   },
   "dependencies": {
-    "@babel/core": "^7.29.7",
-    "@saykit/config": "^0.8.0"
+    "@saykit/config": "^0.9.0"
   },
   "devDependencies": {
+    "@babel/core": "^7.29.7",
     "@types/babel__core": "^7.20.5"
   },
+  "peerDependencies": {
+    "@babel/core": "^7.0.0 || ^8.0.0"
+  },
   "scripts": {
     "check": "tsc --noEmit",
     "build": "tsdown"