@saykit/config 0.9.0 → 0.10.0

package/README.md

@@ -51,7 +51,7 @@ have a file yet are bootstrapped with an empty, header-only catalogue so a TMS c
 existing translation files are left untouched. Translated content is owned by your TMS.
 
 At load time (via the unplugin or Babel plugin), each locale module is filled from its fallback
-chain, so an untranslated key resolves to a fallback locale and ultimately the source string — the
+chain, so an untranslated key resolves to a fallback locale and ultimately the source string, the
 runtime still loads a single locale.
 
 `saykit clean` only ever subtracts from non-source locales: it drops entries that no longer exist in

package/dist/features/loader/index.d.cts

@@ -2,7 +2,7 @@ import { n as Config } from "../../shapes-CRlXtss0.cjs";
 //#region src/features/loader/resolve.d.ts
 /**
  * The config file {@link resolveConfig} would load, for callers that need the
- * path itself rather than its contents — salting a bundler's cache key with it,
+ * path itself rather than its contents, salting a bundler's cache key with it,
  * for one, since what a catalogue assembles into depends on the config.
  */
 declare function resolveConfigFile(name?: string): string;

package/dist/features/loader/index.d.mts

@@ -2,7 +2,7 @@ import { n as Config } from "../../shapes-CRlXtss0.mjs";
 //#region src/features/loader/resolve.d.ts
 /**
  * The config file {@link resolveConfig} would load, for callers that need the
- * path itself rather than its contents — salting a bundler's cache key with it,
+ * path itself rather than its contents, salting a bundler's cache key with it,
  * for one, since what a catalogue assembles into depends on the config.
  */
 declare function resolveConfigFile(name?: string): string;

package/dist/features/messages/index.d.cts

@@ -3,17 +3,15 @@
  * The ICU argument types a macro can author, and the named styles each accepts.
  *
  * A style may also be a skeleton, which is where the formats these names have
- * no word for live — see {@link validateArgumentStyle}.
+ * no word for live; see {@link validateArgumentStyle}.
  *
- * `currency` is deliberately absent from `number`. MF1 has nowhere to write the
- * currency code — it comes from the formatter's configuration, not the message
- * — so `{price, number, currency}` formats as a bare number at runtime rather
- * than an amount. Currency belongs to a skeleton, `::currency/EUR`, which names
- * the code and which the formatter does honour.
+ * `currency` is deliberately absent from `number`: MF1 has nowhere to write the
+ * code, so `{price, number, currency}` formats as a bare number. Currency
+ * belongs to a skeleton, `::currency/EUR`, which the formatter does honour.
  *
- * `spellout`, RBNF `ordinal`, and `choice` are absent by decision rather than
- * oversight: the first two are ICU4J/ICU4C rule-based formats with no `Intl`
- * equivalent, and the third is deprecated in ICU itself in favour of `plural`.
+ * `spellout`, RBNF `ordinal` and `choice` are absent by decision: the first two
+ * are ICU4J/ICU4C rule-based formats with no `Intl` equivalent, and the third
+ * is deprecated in ICU itself in favour of `plural`.
  */
 declare const ARGUMENT_STYLES: {
   readonly number: readonly ["integer", "percent"];
@@ -27,13 +25,12 @@ declare function isArgumentType(kind: string): kind is ArgumentType;
  * Reject an argument style the formatter cannot honour, while the style is
  * still attached to a file and a line.
  *
- * A style is a bare string in the source and a bare string in the catalogue, so
- * nothing between here and the runtime has an opinion about it. Left unchecked,
- * a typo like `{d, date, meduim}` extracts to a catalogue entry that looks
- * perfectly normal and only misformats once it reaches a user.
+ * A style is a bare string in the source and in the catalogue, so nothing
+ * between here and the runtime has an opinion about it. Left unchecked, a typo
+ * like `{d, date, meduim}` only misformats once it reaches a user.
  *
- * Three forms are accepted: a named style, a `::`-prefixed skeleton, and — for
- * a number — a literal pattern such as `#,##0.00`.
+ * Three forms are accepted: a named style, a `::`-prefixed skeleton, and, for
+ * a number, a literal pattern such as `#,##0.00`.
  */
 declare function validateArgumentStyle(type: ArgumentType, style: string): void;
 //#endregion
@@ -44,25 +41,21 @@ declare const AUTO_INCREMENT_IDENTIFIER: unique symbol;
  *
  * Under `plural` and `ordinal` a number names an exact value, spelled `=0`, and
  * so is distinct from the CLDR category that would otherwise match it. `select`
- * has no such syntax — its cases are literal string matches, and `=0` there is
- * a parse error — so a numeric key stays bare, where it matches both `0` and
+ * has no such syntax, so a numeric key stays bare and matches both `0` and
  * `'0'`.
  *
- * Digits are read literally rather than coerced, because everything JavaScript
- * is willing to call a number is not: `''`, `' '`, and `'+0'` all coerce to
- * `=0`, which would pass for a key that selects zero and quietly leave the
- * author's own key out of the catalogue. Anything else stays a key, where the
- * whitespace or punctuation that made it numeric-looking is caught.
+ * Digits are read literally rather than coerced: `''`, `' '` and `'+0'` all
+ * coerce to `=0`, which would pass for a key selecting zero and leave the
+ * author's own key out of the catalogue.
  */
 declare function getBranchCase(kind: string, identifier: string | typeof AUTO_INCREMENT_IDENTIFIER): string;
 /**
  * Reject a branch key ICU cannot express, while the key is still attached to a
  * file and a line.
  *
- * A hyphenated string union is ordinary application code and typechecks,
- * builds, and extracts to a catalogue entry that looks perfectly normal — the
- * only sign of trouble is a parse error at format time, in a message whose
- * source is long gone.
+ * A hyphenated string union is ordinary application code: it typechecks,
+ * builds, and extracts to a normal-looking catalogue entry, and the only sign
+ * of trouble is a parse error at format time.
  */
 declare function validateBranchIdentifier(kind: string, identifier: string | typeof AUTO_INCREMENT_IDENTIFIER): void;
 /**
@@ -86,7 +79,7 @@ declare class LiteralMessage extends Base {
 }
 /**
  * An ICU argument type and style, e.g. `{n, number, percent}`. A style is
- * optional — `{n, number}` is the type's default formatting.
+ * optional: `{n, number}` is the type's default formatting.
  *
  * Both are kept as the ICU strings they are written as, rather than as `Intl`
  * options, because the catalogue is the source of truth and only the ICU
@@ -158,19 +151,16 @@ declare function convertMessageToIcu(message: Message): string;
  * Quoting for text that has to survive a message format unchanged.
  *
  * This lives beside the converter rather than in a transform because it belongs
- * to the format being written, not to the syntax being read. A literal is the
- * same literal whether it came from a template literal or from JSX, and the
- * moment there is a second target format its reserved characters — and the way
- * it spells an escape — are its own.
+ * to the format being written, not the syntax being read: a literal is the same
+ * literal whether it came from a template literal or from JSX.
  */
 /**
  * Escape literal text so ICU MessageFormat 1 reads it as the text it is.
  *
  * MF1 escapes with an apostrophe: a run wrapped in one is taken literally, and a
- * doubled apostrophe is a single apostrophe. The subtlety is that an apostrophe
- * only opens a quoted run when a character that needs quoting follows it —
- * anything else and the apostrophe is itself literal. So `'#'` is a real escape
- * inside a plural and the three characters `'#'` anywhere else, which is why
+ * doubled apostrophe is a single apostrophe. An apostrophe only opens a quoted
+ * run when a character that needs quoting follows it, so `'#'` is a real escape
+ * inside a plural and three literal characters anywhere else, which is why
  * `hash` has to be told rather than assumed.
  *
  * @param text Literal text as the author wrote it
@@ -183,7 +173,7 @@ declare function escapeIcuLiteral(text: string, hash?: boolean): string;
 /**
  * Hashed in userland rather than with `node:crypto`, because this runs wherever
  * a bundler runs it. `createHash` is one of the entry points `unenv` leaves
- * unimplemented — "[unenv] crypto.createHash is not implemented yet!" — so a
+ * unimplemented, "[unenv] crypto.createHash is not implemented yet!", so a
  * plugin reaching for it throws in a Nitro or workerd build. The Web Crypto
  * equivalent, `subtle.digest`, is async, and an id is resolved from a
  * synchronous extraction pass.

package/dist/features/messages/index.d.mts

@@ -3,17 +3,15 @@
  * The ICU argument types a macro can author, and the named styles each accepts.
  *
  * A style may also be a skeleton, which is where the formats these names have
- * no word for live — see {@link validateArgumentStyle}.
+ * no word for live; see {@link validateArgumentStyle}.
  *
- * `currency` is deliberately absent from `number`. MF1 has nowhere to write the
- * currency code — it comes from the formatter's configuration, not the message
- * — so `{price, number, currency}` formats as a bare number at runtime rather
- * than an amount. Currency belongs to a skeleton, `::currency/EUR`, which names
- * the code and which the formatter does honour.
+ * `currency` is deliberately absent from `number`: MF1 has nowhere to write the
+ * code, so `{price, number, currency}` formats as a bare number. Currency
+ * belongs to a skeleton, `::currency/EUR`, which the formatter does honour.
  *
- * `spellout`, RBNF `ordinal`, and `choice` are absent by decision rather than
- * oversight: the first two are ICU4J/ICU4C rule-based formats with no `Intl`
- * equivalent, and the third is deprecated in ICU itself in favour of `plural`.
+ * `spellout`, RBNF `ordinal` and `choice` are absent by decision: the first two
+ * are ICU4J/ICU4C rule-based formats with no `Intl` equivalent, and the third
+ * is deprecated in ICU itself in favour of `plural`.
  */
 declare const ARGUMENT_STYLES: {
   readonly number: readonly ["integer", "percent"];
@@ -27,13 +25,12 @@ declare function isArgumentType(kind: string): kind is ArgumentType;
  * Reject an argument style the formatter cannot honour, while the style is
  * still attached to a file and a line.
  *
- * A style is a bare string in the source and a bare string in the catalogue, so
- * nothing between here and the runtime has an opinion about it. Left unchecked,
- * a typo like `{d, date, meduim}` extracts to a catalogue entry that looks
- * perfectly normal and only misformats once it reaches a user.
+ * A style is a bare string in the source and in the catalogue, so nothing
+ * between here and the runtime has an opinion about it. Left unchecked, a typo
+ * like `{d, date, meduim}` only misformats once it reaches a user.
  *
- * Three forms are accepted: a named style, a `::`-prefixed skeleton, and — for
- * a number — a literal pattern such as `#,##0.00`.
+ * Three forms are accepted: a named style, a `::`-prefixed skeleton, and, for
+ * a number, a literal pattern such as `#,##0.00`.
  */
 declare function validateArgumentStyle(type: ArgumentType, style: string): void;
 //#endregion
@@ -44,25 +41,21 @@ declare const AUTO_INCREMENT_IDENTIFIER: unique symbol;
  *
  * Under `plural` and `ordinal` a number names an exact value, spelled `=0`, and
  * so is distinct from the CLDR category that would otherwise match it. `select`
- * has no such syntax — its cases are literal string matches, and `=0` there is
- * a parse error — so a numeric key stays bare, where it matches both `0` and
+ * has no such syntax, so a numeric key stays bare and matches both `0` and
  * `'0'`.
  *
- * Digits are read literally rather than coerced, because everything JavaScript
- * is willing to call a number is not: `''`, `' '`, and `'+0'` all coerce to
- * `=0`, which would pass for a key that selects zero and quietly leave the
- * author's own key out of the catalogue. Anything else stays a key, where the
- * whitespace or punctuation that made it numeric-looking is caught.
+ * Digits are read literally rather than coerced: `''`, `' '` and `'+0'` all
+ * coerce to `=0`, which would pass for a key selecting zero and leave the
+ * author's own key out of the catalogue.
  */
 declare function getBranchCase(kind: string, identifier: string | typeof AUTO_INCREMENT_IDENTIFIER): string;
 /**
  * Reject a branch key ICU cannot express, while the key is still attached to a
  * file and a line.
  *
- * A hyphenated string union is ordinary application code and typechecks,
- * builds, and extracts to a catalogue entry that looks perfectly normal — the
- * only sign of trouble is a parse error at format time, in a message whose
- * source is long gone.
+ * A hyphenated string union is ordinary application code: it typechecks,
+ * builds, and extracts to a normal-looking catalogue entry, and the only sign
+ * of trouble is a parse error at format time.
  */
 declare function validateBranchIdentifier(kind: string, identifier: string | typeof AUTO_INCREMENT_IDENTIFIER): void;
 /**
@@ -86,7 +79,7 @@ declare class LiteralMessage extends Base {
 }
 /**
  * An ICU argument type and style, e.g. `{n, number, percent}`. A style is
- * optional — `{n, number}` is the type's default formatting.
+ * optional: `{n, number}` is the type's default formatting.
  *
  * Both are kept as the ICU strings they are written as, rather than as `Intl`
  * options, because the catalogue is the source of truth and only the ICU
@@ -158,19 +151,16 @@ declare function convertMessageToIcu(message: Message): string;
  * Quoting for text that has to survive a message format unchanged.
  *
  * This lives beside the converter rather than in a transform because it belongs
- * to the format being written, not to the syntax being read. A literal is the
- * same literal whether it came from a template literal or from JSX, and the
- * moment there is a second target format its reserved characters — and the way
- * it spells an escape — are its own.
+ * to the format being written, not the syntax being read: a literal is the same
+ * literal whether it came from a template literal or from JSX.
  */
 /**
  * Escape literal text so ICU MessageFormat 1 reads it as the text it is.
  *
  * MF1 escapes with an apostrophe: a run wrapped in one is taken literally, and a
- * doubled apostrophe is a single apostrophe. The subtlety is that an apostrophe
- * only opens a quoted run when a character that needs quoting follows it —
- * anything else and the apostrophe is itself literal. So `'#'` is a real escape
- * inside a plural and the three characters `'#'` anywhere else, which is why
+ * doubled apostrophe is a single apostrophe. An apostrophe only opens a quoted
+ * run when a character that needs quoting follows it, so `'#'` is a real escape
+ * inside a plural and three literal characters anywhere else, which is why
  * `hash` has to be told rather than assumed.
  *
  * @param text Literal text as the author wrote it
@@ -183,7 +173,7 @@ declare function escapeIcuLiteral(text: string, hash?: boolean): string;
 /**
  * Hashed in userland rather than with `node:crypto`, because this runs wherever
  * a bundler runs it. `createHash` is one of the entry points `unenv` leaves
- * unimplemented — "[unenv] crypto.createHash is not implemented yet!" — so a
+ * unimplemented, "[unenv] crypto.createHash is not implemented yet!", so a
  * plugin reaching for it throws in a Nitro or workerd build. The Web Crypto
  * equivalent, `subtle.digest`, is async, and an id is resolved from a
  * synchronous extraction pass.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@saykit/config",
-  "version": "0.9.0",
+  "version": "0.10.0",
   "description": "CLI and configuration tooling for saykit",
   "keywords": [
     "cli",