-
Notifications
You must be signed in to change notification settings - Fork 24
feat: accept Uint8Arrays in place of Buffers #61
Conversation
|
Does the |
I'm not sure what changes with
|
|
Oh I was wrong in suggesting that:
I do see now that this is not the case, it is used in the code not just test |
|
@rvagg I have addressed your remark by pulling in |
|
You need to cut a new version of web-encoding @Gozala, the 1.0.1 package is 110Mb and unpacked is 356Mb thanks to a bundled version of Linux Chromium in a .cache directory. btw if this comes from consuming puppeteer then check out https://github.com/rvagg/polendina#minimising-puppeteers-size to reduce the size, having ~300Mb extra junk in each of my package directories even for devdeps drives me mad. |
rvagg
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, although I think it should get a ^1.0.2 for web-encoding before releasing though, and you might want to consider tweaking the README to mention Uint8Arrays, it's a bit ambiguous at the moment with "buffer" (lower-case) and that could become "Buffer or Uint8Array".
I'm guessing it is coming from playwright-test, which I end up using because I could not figure out rvagg/polendina#10. BTW you and @hugomrdias might want to consider converging two. |
I end up adding |
|
There so not be any .cache or bundle browser in the playwright-test npm package install, it lazy downloads the browser binary to the OS temp folder only once per version, if this is not happening please open an issue and i will fix it! |
|
Thank you @Gozala |
This pull request relaxes input type from
BuffertoUint8Array. It still returnsBuffers back to ensure backwards compatibility. It also adds missing TS JSDoc comments as they helped me understand interfaces between components.