json-rpc-middleware-stream: Allow using with either readable-stream v3/v4

[legobeat]

Explanation

Add support for readable-stream v4 while not breaking v3.

References

Changelog

@metamask/json-rpc-middleware-stream

• CHANGED: Package now supports readable-stream v4 as well as v3.

Checklist

• [x] I've updated the test suite for new or updated code as appropriate
• [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
• [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	+1	63.3 kB	types
npm/[email protected]	None	0	292 kB	kilianvalkhof

🚮 Removed packages: npm/@types/[email protected], npm/[email protected]

View full report↗︎

[legobeat]

@mcmire Failing on this constraint:

➤ YN0024: @metamask/json-rpc-middleware-stream must depend on readable-stream via a range optionally starting with ^ or ~, but uses ^3.6.2 || ^4.5.2 instead (in dependencies)

Do you think we can open up for this union range?