Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Expo managed workflow - crash on web
See original GitHub issueDescribe the bug Importing dependencies from @stripe/stripe-react-native causes app to crash on Expo managed workflow - web.
To Reproduce Steps to reproduce the behavior:
- Create new expo managed workflow project
expo install @stripe/stripe-react-native- import stripe dependencies into component
- expo start --web
- See errors
Expected behavior No errors unless stripe components are actually used at runtime.
Additional context I’m aware that web isn’t supported, but it would be nice if it would at least build so I could run my app. I don’t plan to render any stripe components in the browser at runtime. Currently I can’t figure out a way to make Webpack exclude this dependency. Any help would be greatly appreciated.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:12
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@olaurendeau I have a workaround for now. I’ve implemented separate application entry points for mobile and web, with a basic dependency injection container to abstract away the platform dependent components. It’s not ideal, but it works.
No. All the errors were introduced when I added the Stripe library.