Releases · I-am-abdulazeez/stunk

Allow undefined initial values: chunk() now accepts undefined as an initial value, making it easier to work with optional state
Enhanced middleware support: Middleware can now process and return undefined values throughout the chain
Improved TypeScript support: Better type inference for optional values like chunk<User | undefined>(undefined)

🔧 Technical Details

Removed restriction on undefined values in chunk creation and middleware processing
null values remain restricted to prevent common JavaScript pitfalls
All existing functionality remains unchanged

Usage Example

// ✅ Now possible
const userChunk = chunk<User | undefined>(undefined);
const statusChunk = chunk<"loading" | "success" | undefined>(undefined);

// ✅ Still works as before
const nameChunk = chunk("John");
const countChunk = chunk(0);

// ❌ Still throws (null remains restricted)  
const badChunk = chunk(null);

What's Changed

Allow undefine value for initial value by @I-am-abdulazeez in #29
fix: update version to 2.5.0 in package.json by @I-am-abdulazeez in #30

Full Changelog: v2.4.0...v2.5.0

Contributors

I-am-abdulazeez

Assets 2

08 Jun 19:20

I-am-abdulazeez

v2.4.0

fd6bedc

v2.4.0

🎉 What’s New in Stunk v2.4.0
✅ set() now validates keys
Trying to update a non-existent state property? Stunk will now warn you — no more silent bugs.

⚡️ asyncChunk() just got smarter
– Support for refresh, cacheTime, staleTime, and refetchInterval
– enabled flag for conditional fetching
– Internal caching & staleness logic
– Param-based reload, refresh, and setParams now fully supported

🧼 Built-in cleanup
Timers and intervals are automatically cleared — no memory leaks.

Still simple. Still reactive. Now even more powerful.
Update to v2.4.0 and level up your state game.

Assets 2