-
Notifications
You must be signed in to change notification settings - Fork 52
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
setAsEmptyObject - null Exception #107
Comments
@kriszyp |
Yes, and I don't know why github isn't properly showing it, looks linked to me, but added a test for this here ab6dcc4, and it doesn't seem to reproduce for me. I am doing something wrong? |
hey @kriszyp, I deleted my previous comment and write this one. It is much more simple. I cloned your repo and wrote a test. Everything works, just like your unit test, as long as I import the lib locally (not using npm install). Note: Doesn't matter if I use commonJS or ES module. Same results. Any idea why this is happening? The test code:
|
For some reason the built/dist version in the last release is not up-to-date with the source. I will release a new version, and make sure it is fully built, as soon as I figure out how to fix #109 . |
Published an update in 1.9.2. |
Cool Thanks! Verified the new version and it does solve the issue. Thanks again! P.S. Will continue to test backward compatibility. If we find anything - will let you know in yet another issue ;) |
Hi @kriszyp ,
I am running the test code attached below on Node.js 18.16 with msgpackr 1.9 using the 2 new flags and get this error:
When turning off the 2 flags, it works well.
Thanks,
Gonen.
The test code:
The text was updated successfully, but these errors were encountered: