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

fix: replace node buffers with uint8arrays #140

Merged
merged 2 commits into from
Aug 7, 2020

Conversation

achingbrain
Copy link
Member

All uses of node Buffers have been replaced with Uint8Arrays.

Also redundant modules have been removed from package.json

BREAKING CHANGES:

  • Where node Buffers were returned, now Uint8Arrays are
  • The .buffer property has been renamed .bytes similar to [email protected]

@achingbrain
Copy link
Member Author

test/types.spec.ts - what is this file for? It looks like a test, but doesn't assert anything and causes linting to fail.

@jacobheun
Copy link
Contributor

test/types.spec.ts - what is this file for? It looks like a test, but doesn't assert anything and causes linting to fail.

It's a type test that's run with npx tsc, it's verifying the type exports are being done properly.

All uses of node Buffers have been replaced with Uint8Arrays.

Also redundant modules have been removed from package.json

BREAKING CHANGES:

- Where node Buffers were returned, now Uint8Arrays are
- The `.buffer` property has been renamed `.bytes` similar to [email protected]
@achingbrain achingbrain force-pushed the fix/replace-node-buffers-with-uint8arrays branch from 29354ad to 30186c4 Compare August 7, 2020 14:25
@achingbrain
Copy link
Member Author

It's a type test

Call me old fashioned, but tests should do more than just compile something 😆

I've reinstated the file but downgraded aegir as the current version tries to lint and run that file as a test which fails.

@jacobheun jacobheun merged commit 53398f5 into master Aug 7, 2020
@jacobheun jacobheun deleted the fix/replace-node-buffers-with-uint8arrays branch August 7, 2020 14:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants