babel-plugin-saykit 0.9.1 → 0.10.0

package/dist/index.d.cts

@@ -12,9 +12,9 @@ interface Options {
    * `'inline'` (the default) replaces the import with the assembled record, so
    * the Babel plugin is enough on its own. The cost is that the record lands in
    * the importing module, which a bundler only re-reads when that module's own
-   * bytes change — editing a catalogue will not hot-reload.
+   * bytes change, editing a catalogue will not hot-reload.
    *
-   * `'module'` leaves the import for a bundler integration to serve —
+   * `'module'` leaves the import for a bundler integration to serve, either
    * `babel-plugin-saykit/next` or `babel-plugin-saykit/metro`. Set this
    * whenever one of those is wired up, or the import gets inlined before the
    * integration is ever asked for the module.

package/dist/metro/index.d.cts

@@ -16,7 +16,7 @@ interface MetroConfig {
  * ```
  *
  * 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
+ * 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

package/dist/metro/transformer.d.cts

@@ -11,8 +11,8 @@ interface TransformerConfig {
  * 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.
+ * catalogue's own source, leaving the file a real module whose sha1, and
+ * therefore Metro's transform cache entry, moves whenever it is edited.
  */
 declare function transform(transformerConfig: TransformerConfig, projectRoot: string, filename: string, data: Buffer, options: unknown): Promise<unknown>;
 declare function getCacheKey(transformerConfig: TransformerConfig, options?: unknown): string;

package/dist/next/index.d.cts

@@ -25,11 +25,11 @@ interface WebpackConfig {
  * export default withSayKit({});
  * ```
  *
- * Pair it with `catalogues: 'module'` on the Babel plugin — the plugin has to
+ * Pair it with `catalogues: 'module'` on the Babel plugin, which 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
+ * 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.
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "babel-plugin-saykit",
-  "version": "0.9.1",
+  "version": "0.10.0",
   "description": "Babel plugin for SayKit",
   "keywords": [
     "i18n",
@@ -48,7 +48,7 @@
     "provenance": true
   },
   "dependencies": {
-    "@saykit/config": "^0.9.1"
+    "@saykit/config": "^0.10.0"
   },
   "devDependencies": {
     "@babel/core": "^7.29.7",