chore(deps): bump nipplejs from 0.10.2 to 1.0.4

[dependabot]

Bumps nipplejs from 0.10.2 to 1.0.4.

Release notes

Sourced from nipplejs's releases.

v1.0.4

NippleJS v1.0.4

A small patch release fixing a regression in multi-manager pointer event handling. Thanks again @​akromann for the follow-up in #246.

🌐 Documentation · 🎮 Interactive Demos · 📦 npm

---

🐛 Bug Fixes

• Multiple managers closed each other when using pointer events — Factory.cleanInactiveTouches() treated [evt.identifier] as the full set of active pointers for non-touch events, causing every joystick with a different pointerId to be force-ended on each pointerdown/pointerup. The cleanup now runs only for TouchEvents (which carry the complete touches list); per-pointer pointerup/pointercancel already handles its own cleanup. Also snapshots the joystick map before iterating to avoid mutation during the loop. (2c087f9)
• TouchList iteration tightened — processEvents() now wraps evt.changedTouches with Array.from() for broader TypeScript/iterator compatibility. (653b81d)

---

✅ Tests

• Added regression coverage for cleanInactiveTouches ensuring pointer events don't force-end sibling joysticks, and that TouchEvent cleanup still removes truly inactive joysticks. (2721cf4)

---

Full Changelog: yoannmoinet/nipplejs@v1.0.3...v1.0.4

v1.0.3

NippleJS v1.0.3

A small patch release fixing TypeScript event handler overload inference and a multi-manager DOM containment bug. Thanks @​akromann for the report and fixes in #245.

🌐 Documentation · 🎮 Interactive Demos · 📦 npm

---

🐛 Bug Fixes

• Multiple managers couldn't open joysticks simultaneously — Joystick.start() checked document.body.contains() to decide whether to re-add the element, which returned true for any joystick already mounted anywhere in the DOM. This caused a manager to skip mounting its joystick when another manager already had one active. Now uses zone.contains() so each manager checks its own zone. (6418df2)
• TypeScript on() handler type was unusable without as any — SuperEventType resolved to a union of all possible event payloads instead of narrowing based on the event name, forcing users to cast handlers. Added a generic parameter so the handler type narrows correctly to the matching EventDataMap entry. (2ff4c51)

---

Full Changelog: yoannmoinet/nipplejs@v1.0.2...v1.0.3

v1.0.2

NippleJS v1.0.2

A small patch release focused on fixing static-mode joystick reuse on touch devices.

🌐 Documentation · 🎮 Interactive Demos · 📦 npm

---

... (truncated)

Commits

• ea425b3 chore: bump version to 1.0.4
• 2721cf4 test(factory): add regression test for pointer events clean up with multiple ...
• 653b81d fix(utils): use Array.from() to iterate TouchList for broader TS compatibility
• 2c087f9 fix(factory): skip cleanInactiveTouches for pointer events
• b8b5d22 chore: bump version to 1.0.3
• 6418df2 fix(joystick): use zone.contains() instead of document.body.contains()
• 2ff4c51 fix(types): add T to SuperEventType to fix TypeScript overload resolution
• ae6cb47 chore: bump version to 1.0.2
• eafdca2 refactor(Collection): mark joysticks reusable on end instead of hidden
• 25c0496 Fix static joystick
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for nipplejs since your current version.

[dependabot]

Assignees

The following users could not be added as assignees: @maw629. Either the username does not exist or it does not have the correct permissions to be added as an assignee.

Please fix the above issues or remove invalid values from dependabot.yml.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details
npm/nipplejs	1.0.4	🟢 4.8	Details Check Score Reason Maintained 🟢 10 14 commit(s) and 10 issue activity found in the last 90 days -- score normalized to 10 Code-Review ⚠️ 1 Found 3/19 approved changesets -- score normalized to 1 Token-Permissions ⚠️ 0 detected GitHub workflow tokens with excessive permissions CII-Best-Practices ⚠️ 0 no effort to earn an OpenSSF best practices badge detected Dangerous-Workflow 🟢 10 no dangerous workflow patterns detected Security-Policy ⚠️ 0 security policy file not detected Binary-Artifacts 🟢 10 no binaries found in the repo License 🟢 10 license file detected Signed-Releases ⚠️ -1 no releases found Fuzzing ⚠️ 0 project is not fuzzed Branch-Protection ⚠️ -1 internal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md Packaging 🟢 10 packaging workflow detected Pinned-Dependencies ⚠️ 0 dependency not pinned by hash detected -- score normalized to 0 SAST ⚠️ 0 SAST tool is not run on all commits -- score normalized to 0

Scanned Files

• package-lock.json