Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(release): v2 #59

Merged
merged 96 commits into from
Jun 22, 2023
Merged

chore(release): v2 #59

merged 96 commits into from
Jun 22, 2023

Conversation

jonasgloning
Copy link
Member

No description provided.

SnowyCoder and others added 30 commits October 1, 2020 21:40
Fixes peerjs issue 715
When serializing an object that contains `undefined` as a value,
the current packer code incorrectly serializes the value as `null`
(0xc0). `null` and `undefined` are not the same thing, and should
not be serialized into the same binary representation.

Strangely, the unpacker actually does support unpacking `undefined`
values using the binary representation 0xc1.

There was an old pull request (#4) that seems to address this along
with a bunch of other seemingly unrelated changes. The GitHub UI
seems to think that the PR was merged manually, but the code that
fixes this issue never actually made it into the master branch as
far as I can tell.

Another option is to omit any keys with `undefined` values. This is
what `JSON.stringify` does as `JSON` does not support `undefined`
natively. When deserialized, the semantics are mostly correct, as
accessing a key that doesn't exist will give you `undefined`. This
is slightly more efficient, I suppose and maintain the exact same
behavior between binarypack and JSON serialization which is a good
thing. However, you can observe the difference with `Object.keys`,
`Object.hasOwnProperty`, etc.
The code was assuming that they had UTF-8 length 6 instead of 4, causing
a crash on any character above U+FFFF.

Also handle unpaired surrogates correctly.
pack_string / unpack_string: handle chars above U+FFFF
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
refactor: typescript strict mode compliant
Githubs runners are slow
* Add renovate.json

* ci: configure renovate

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Jonas Gloning <[email protected]>
renovate bot and others added 26 commits May 15, 2023 22:31
@jonasgloning jonasgloning changed the title Release v2 chore(release): v2 Jun 22, 2023
@jonasgloning jonasgloning merged commit 51d0678 into stable Jun 22, 2023
@jonasgloning
Copy link
Member Author

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants