Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@text-rendering-toolkit/font@0.2.0

Minor Changes

• aca5e1a: Report unusable arguments with each package's own error type.

  generateSdf, the Text and TextResources constructors, and loadFont each
  read a field off their argument before validating it, so null, undefined, a
  primitive, or a throwing getter escaped as a raw TypeError — or as the
  caller's own error — instead of the type each function documents. generateSdf
  also read width and viewBox more than once, so a getter returning different
  values could size a raster by a number that was never validated.

  Each entry point now copies its argument once, up front, and reports anything
  unreadable as InvalidSdfInputError, InvalidTextInputError, or
  InvalidFontError with the original attached as cause. loadFont reports a
  detached ArrayBuffer — or a view onto one — the same way.

  Every error this toolkit wraps now carries the original as cause, including
  two that previously discarded it: shaping failures raised by HarfBuzz, and font
  loads that failed during parsing.

  @text-rendering-toolkit/font is a minor because InvalidFontError extends
  Error rather than TypeError: code catching TypeError around loadFont to
  handle a detached buffer no longer matches. The SDF and Three errors both extend
  TypeError, so callers catching that continue to match.

@text-rendering-toolkit/layout@0.2.0

Minor Changes

• aca5e1a: Contain font handle failures inside the layout error contract.

  layoutText and layoutPreparedText previously let errors from
  @text-rendering-toolkit/font escape unwrapped — a typo in a style's variation
  axis or feature string surfaced as InvalidShapingInputError, and a handle
  disposed mid-layout surfaced as DisposedFontHandleError, neither of which the
  documented contract mentioned. Callers had to catch error types from a package
  they may not import.

  Every call into a caller-owned FontHandle — registry lookup, coverage test,
  shaping, and metrics — is now converted to a TextPreparationError with the new
  code: 'font-error', with the original attached as cause. Branch on code
  and inspect cause when the underlying detail matters.

  TextPreparationErrorCode gains the 'font-error' member, and
  TextPreparationError now accepts and forwards a cause.

Patch Changes

• Updated dependencies [aca5e1a]
  • @text-rendering-toolkit/font@0.2.0

@text-rendering-toolkit/sdf@0.2.0

Patch Changes

• aca5e1a: Report unusable arguments with each package's own error type.

  generateSdf, the Text and TextResources constructors, and loadFont each
  read a field off their argument before validating it, so null, undefined, a
  primitive, or a throwing getter escaped as a raw TypeError — or as the
  caller's own error — instead of the type each function documents. generateSdf
  also read width and viewBox more than once, so a getter returning different
  values could size a raster by a number that was never validated.

  Each entry point now copies its argument once, up front, and reports anything
  unreadable as InvalidSdfInputError, InvalidTextInputError, or
  InvalidFontError with the original attached as cause. loadFont reports a
  detached ArrayBuffer — or a view onto one — the same way.

  Every error this toolkit wraps now carries the original as cause, including
  two that previously discarded it: shaping failures raised by HarfBuzz, and font
  loads that failed during parsing.

  @text-rendering-toolkit/font is a minor because InvalidFontError extends
  Error rather than TypeError: code catching TypeError around loadFont to
  handle a detached buffer no longer matches. The SDF and Three errors both extend
  TypeError, so callers catching that continue to match.

@text-rendering-toolkit/three-webgpu@0.2.0

Patch Changes

• aca5e1a: Report unusable arguments with each package's own error type.

  generateSdf, the Text and TextResources constructors, and loadFont each
  read a field off their argument before validating it, so null, undefined, a
  primitive, or a throwing getter escaped as a raw TypeError — or as the
  caller's own error — instead of the type each function documents. generateSdf
  also read width and viewBox more than once, so a getter returning different
  values could size a raster by a number that was never validated.

  Each entry point now copies its argument once, up front, and reports anything
  unreadable as InvalidSdfInputError, InvalidTextInputError, or
  InvalidFontError with the original attached as cause. loadFont reports a
  detached ArrayBuffer — or a view onto one — the same way.

  Every error this toolkit wraps now carries the original as cause, including
  two that previously discarded it: shaping failures raised by HarfBuzz, and font
  loads that failed during parsing.

  @text-rendering-toolkit/font is a minor because InvalidFontError extends
  Error rather than TypeError: code catching TypeError around loadFont to
  handle a detached buffer no longer matches. The SDF and Three errors both extend
  TypeError, so callers catching that continue to match.

• Updated dependencies [aca5e1a]

• Updated dependencies [aca5e1a]

  • @text-rendering-toolkit/sdf@0.2.0
  • @text-rendering-toolkit/layout@0.2.0