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

Research and implement a solution that doesn't require a custom metro.config.js file when using react native SDK #156

Open
standemchuk opened this issue Oct 13, 2021 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers invalid This doesn't seem right

Comments

@standemchuk
Copy link

Background

During our work with the React Native and Expo SDKs we had to configure the bundler to use browserify versions of certain libraries like crypto, stream, and randomBytes. This creates unnecessary additional configuration steps when starting to use our SDK and reduces the developer experience. More information here:

What is needed to be done

Research and implement a solution that doesn't require any additional configuration besides npm install-ing the package. This could be in a form of different packages solving the problem or in a form of configuration being done during the installation phase (post-install hook?)

Why is this needed

We want to improve the developer experience of the developers using our SDK.

@standemchuk standemchuk added enhancement New feature or request good first issue Good for newcomers invalid This doesn't seem right labels Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

1 participant