@tootallnate/once
3.0.1 · 9 Feb 2026MIT60.7M / weekRepositoryHomepagenpmAtom feed
Upgrading @tootallnate/once From 1.1.2 to 2.0.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 1
- change to make
- 0
- advisories fixed
- 2
- new
- 2
- fixes
Before you upgrade
Tick each one off as you go- Breaking2.0.0
Security
1 advisory still affects 2.0.0
- @tootallnate/once vulnerable to Incorrect Control Flow Scopinglow · GHSA-vpq2-c234-7xj6
Upgrading to 2.0.1 clears it.
Release by release
- Breaking
Big refactor for v2
- New
Add
README.md: d00821f35b44ed48466b8e5d202c2788e3688df6 - New
Create LICENSE
- Fixed
c3260138d77811bde3823cebd490ff59b35fe32f
- Fixed
Remove test script
- Breaking
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.