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

feat: react-native support #403

Merged
merged 1 commit into from
Dec 8, 2023
Merged

Conversation

achingbrain
Copy link
Collaborator

React-native doesn't have any node core modules so it must use the pure-js/browser implementations of everything.

React-native doesn't have any node core modules so it must use the
pure-js/browser implementations of everything.
@wemeetagain wemeetagain merged commit 233144f into master Dec 8, 2023
13 checks passed
@wemeetagain wemeetagain deleted the feat/react-native-support branch December 8, 2023 18:32
achingbrain added a commit that referenced this pull request Dec 9, 2023
It turns out this isn't necessary so revert the changes.

Also, we don't depend on node's `util` so no need to override that
in the browser field.
achingbrain added a commit that referenced this pull request Dec 9, 2023
It turns out this isn't necessary so revert the changes.

Also, we don't depend on node's `util` so no need to override that
in the browser field.
wemeetagain pushed a commit that referenced this pull request Dec 9, 2023
It turns out this isn't necessary so revert the changes.

Also, we don't depend on node's `util` so no need to override that
in the browser field.
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