Skip to content

chore(deps): bump @pionjs/pion from 2.13.0 to 2.16.0#152

Merged
megheaiulian merged 1 commit into
mainfrom
dependabot/npm_and_yarn/pionjs/pion-2.16.0
Jun 18, 2026
Merged

chore(deps): bump @pionjs/pion from 2.13.0 to 2.16.0#152
megheaiulian merged 1 commit into
mainfrom
dependabot/npm_and_yarn/pionjs/pion-2.16.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 25, 2026

Copy link
Copy Markdown
Contributor

Bumps @pionjs/pion from 2.13.0 to 2.16.0.

Release notes

Sourced from @​pionjs/pion's releases.

v2.16.0

Minor Changes

  • 6018594: Allow lift to bubble functional state updaters to parent components

    useProperty now resolves the updater function against host[property] before dispatching the event, so ev.detail.value always contains the resolved value. The original updater function is also included in ev.detail.updater for lift to pass to the parent setter, which resolves it against the parent's authoritative state.

    This fixes rapid-fire functional updater calls (e.g., setItems((items) => [...items, item])) producing incorrect state when used with lift, because the child's local state was blocked by preventDefault() and hadn't yet been updated by the parent re-render.

    Breaking changes

    • useProperty.updateProp removed (was internal, not part of public API)
    • useProperty.init removed (was internal, not part of public API)
    • Event detail shape now includes updater field alongside value
    • ev.detail.value is always the resolved value (was undefined for functional updaters)
    • lift now passes ev.detail.updater ?? ev.detail.value to setter (was ev.detail.value)
    • useProperty setter now always dispatches a change event, even if the value is unchanged

v2.15.0

Minor Changes

  • f0dab4f: Detect and stop infinite update loops.

v2.14.0

Minor Changes

  • ad72947: Make Ref<T> align better with lit-html compatibility

    Changed Ref<T> from { current: T; value: T; } to { current: T | undefined; value?: T; }.

    This makes Ref<T> structurally compatible with lit-html's Ref<T> type, allowing pion refs to be used directly with lit-html's ref directive without type errors:

    // Before: Type error
    const popover = useRef<HTMLElement>();
    html`<div ${ref(popover)}></div>`; // Error: Ref<HTMLElement | undefined> ≠ Ref<HTMLElement>
    // After: Works correctly
    const popover = useRef<HTMLElement>();
    html&lt;div ${ref(popover)}&gt;&lt;/div&gt;; // OK

    For users, behavior is identical: ref.current and ref.value still return T | undefined when no initial value is provided. Type narrowing works the same way: if (ref.current) { ref.current.showPopover(); }.

    BREAKING CHANGE: If you explicitly typed refs as Ref<T | undefined>, update to Ref<T>:

    // Before
    const ref: Ref<HTMLElement | undefined> = useRef();

... (truncated)

Changelog

Sourced from @​pionjs/pion's changelog.

2.16.0

Minor Changes

  • 6018594: Allow lift to bubble functional state updaters to parent components

    useProperty now resolves the updater function against host[property] before dispatching the event, so ev.detail.value always contains the resolved value. The original updater function is also included in ev.detail.updater for lift to pass to the parent setter, which resolves it against the parent's authoritative state.

    This fixes rapid-fire functional updater calls (e.g., setItems((items) => [...items, item])) producing incorrect state when used with lift, because the child's local state was blocked by preventDefault() and hadn't yet been updated by the parent re-render.

    Breaking changes

    • useProperty.updateProp removed (was internal, not part of public API)
    • useProperty.init removed (was internal, not part of public API)
    • Event detail shape now includes updater field alongside value
    • ev.detail.value is always the resolved value (was undefined for functional updaters)
    • lift now passes ev.detail.updater ?? ev.detail.value to setter (was ev.detail.value)
    • useProperty setter now always dispatches a change event, even if the value is unchanged

2.15.0

Minor Changes

  • f0dab4f: Detect and stop infinite update loops.

2.14.0

Minor Changes

  • ad72947: Make Ref<T> align better with lit-html compatibility

    Changed Ref<T> from { current: T; value: T; } to { current: T | undefined; value?: T; }.

    This makes Ref<T> structurally compatible with lit-html's Ref<T> type, allowing pion refs to be used directly with lit-html's ref directive without type errors:

    // Before: Type error
    const popover = useRef<HTMLElement>();
    html`<div ${ref(popover)}></div>`; // Error: Ref<HTMLElement | undefined> ≠ Ref<HTMLElement>
    // After: Works correctly
    const popover = useRef<HTMLElement>();
    html&lt;div ${ref(popover)}&gt;&lt;/div&gt;; // OK

    For users, behavior is identical: ref.current and ref.value still return T | undefined when no initial value is provided. Type narrowing works the same way: if (ref.current) { ref.current.showPopover(); }.

    BREAKING CHANGE: If you explicitly typed refs as Ref<T | undefined>, update to Ref<T>:

... (truncated)

Commits
  • 76bb15e [ci] release (#152)
  • 6018594 feat: bubble functional state updaters through lift (#150)
  • 07ce8ae fix: upgrade TypeScript to 6.0.3 and fix tsconfig compatibility (#151)
  • b34f7d7 build(deps): bump the npm_and_yarn group across 1 directory with 7 updates (#...
  • 27e4ece build(deps): bump the npm_and_yarn group across 1 directory with 6 updates (#...
  • 5a481b6 build(deps-dev): bump basic-ftp (#133)
  • 2e6026d build(deps): bump lit-html from 3.3.2 to 3.3.3 (#144)
  • 5eb71d6 build(deps): bump h3 (#126)
  • 8a55760 [ci] release (#146)
  • f0dab4f feat: detect and stop infinite update loops (#145)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [@pionjs/pion](https://github.com/pionjs/pion) from 2.13.0 to 2.16.0.
- [Release notes](https://github.com/pionjs/pion/releases)
- [Changelog](https://github.com/pionjs/pion/blob/main/CHANGELOG.md)
- [Commits](pionjs/pion@v2.13.0...v2.16.0)

---
updated-dependencies:
- dependency-name: "@pionjs/pion"
  dependency-version: 2.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 25, 2026
@megheaiulian megheaiulian merged commit f031032 into main Jun 18, 2026
7 of 8 checks passed
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/pionjs/pion-2.16.0 branch June 18, 2026 05:48
@github-actions

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-06-18 05:49 UTC

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant