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

@wuchale/astro@0.5.0

Minor Changes

• 15d677e: ⚠️ BREAKING: Replace single details object with an array of scope objects and separate filename for heuristic

  The heuristic function now gets called with two arguments: the extracted Text object, and the filename as a string argument. The Text object now has:

  • .body: string[] instead of Message.msgStr
  • .path: Scope[] instead of Message.details - this is an array of different small Scope objects that better conveys nesting information.
  • The rest of the properties are the same as Message

  Therefore if you implement a custom heuristic function you should for example:

  -heuristic: (msg) => {
  +heuristic: (text, file) => {
  -    if (msg.details.element || msg.details.file.endsWith('.foo')) {
  +    if (text.path.some(s => s.type === 'element') || file.endsWith('.foo')) {
           return false
       }
   }

  The scope array is now used to ignore whole sub-trees of ignored elements even if they contain non-ignored elements.

Patch Changes

• Updated dependencies [cd53445, 15d677e]:
  • wuchale@0.26.0

@wuchale/jsx@0.13.0

Minor Changes

• 15d677e: ⚠️ BREAKING: Replace single details object with an array of scope objects and separate filename for heuristic

  The heuristic function now gets called with two arguments: the extracted Text object, and the filename as a string argument. The Text object now has:

  • .body: string[] instead of Message.msgStr
  • .path: Scope[] instead of Message.details - this is an array of different small Scope objects that better conveys nesting information.
  • The rest of the properties are the same as Message

  Therefore if you implement a custom heuristic function you should for example:

  -heuristic: (msg) => {
  +heuristic: (text, file) => {
  -    if (msg.details.element || msg.details.file.endsWith('.foo')) {
  +    if (text.path.some(s => s.type === 'element') || file.endsWith('.foo')) {
           return false
       }
   }

  The scope array is now used to ignore whole sub-trees of ignored elements even if they contain non-ignored elements.

Patch Changes

• Updated dependencies [cd53445, 15d677e]:
  • wuchale@0.26.0

@wuchale/svelte@0.21.0

Minor Changes

• 15d677e: ⚠️ BREAKING: Replace single details object with an array of scope objects and separate filename for heuristic

  The heuristic function now gets called with two arguments: the extracted Text object, and the filename as a string argument. The Text object now has:

  • .body: string[] instead of Message.msgStr
  • .path: Scope[] instead of Message.details - this is an array of different small Scope objects that better conveys nesting information.
  • The rest of the properties are the same as Message

  Therefore if you implement a custom heuristic function you should for example:

  -heuristic: (msg) => {
  +heuristic: (text, file) => {
  -    if (msg.details.element || msg.details.file.endsWith('.foo')) {
  +    if (text.path.some(s => s.type === 'element') || file.endsWith('.foo')) {
           return false
       }
   }

  The scope array is now used to ignore whole sub-trees of ignored elements even if they contain non-ignored elements.

Patch Changes

• Updated dependencies [cd53445, 15d677e]:
  • wuchale@0.26.0

wuchale@0.26.0

Minor Changes

• cd53445: More reliable HMR implementation that doesn't get confused with secondary instances (like the CLI)

• 15d677e: ⚠️ BREAKING: Replace single details object with an array of scope objects and separate filename for heuristic

  The heuristic function now gets called with two arguments: the extracted Text object, and the filename as a string argument. The Text object now has:

  • .body: string[] instead of Message.msgStr
  • .path: Scope[] instead of Message.details - this is an array of different small Scope objects that better conveys nesting information.
  • The rest of the properties are the same as Message

  Therefore if you implement a custom heuristic function you should for example:

  -heuristic: (msg) => {
  +heuristic: (text, file) => {
  -    if (msg.details.element || msg.details.file.endsWith('.foo')) {
  +    if (text.path.some(s => s.type === 'element') || file.endsWith('.foo')) {
           return false
       }
   }

  The scope array is now used to ignore whole sub-trees of ignored elements even if they contain non-ignored elements.

@wuchale/json@0.2.2

Patch Changes

• Updated dependencies [cd53445, 15d677e]:
  • wuchale@0.26.0