Update return type in fromHexStringToBytes for Next.js compatibility #25
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
issue #24
Overview
This PR addresses an issue in the
fromHexStringToBytes
function that was causing errors in Next.js applications. To resolve this, the return type of the function has been changed fromArrayBufferLike
toUint8Array
.Changes
fromHexStringToBytes
fromArrayBufferLike
toUint8Array
to ensure compatibility with Next.js.Testing
The function has been tested locally in a Next.js setup and is working as expected. However, tests in environments such as Cloudflare Workers are pending.
Please review the changes and let me know if there are any concerns or additional adjustments needed. Further testing in other environments will be conducted as needed.