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

Clarify usage within React Native applications #323

Closed
kadamwhite opened this issue Jun 27, 2017 · 3 comments
Closed

Clarify usage within React Native applications #323

kadamwhite opened this issue Jun 27, 2017 · 3 comments

Comments

@kadamwhite
Copy link
Collaborator

#300 establishes that React Native does not bundle all the same dependencies that Node does; we should either depend on these shim libraries directly so that this project can be used independently of environment, or else clarify the React Native-specific requirements somewhere in the docs.

@vijayst
Copy link

vijayst commented Jan 22, 2018

I like to use this package with React native, if possible. As of now, I get a red screen when used with React native. Something to do with bundling.

@magicpriest
Copy link

magicpriest commented Aug 20, 2018

Hello, @kadamwhite
I've recently started development of an mobile app that fetches data from remote blog based on WP, so things are not working OOB.
First of all, after installing and attaching library to some component app will throw error: 'Unable to resolve module "Util" from ../wpapi/lib/endpoint-request.js'.
So, why not install 'util'? Because react-native stack is common to browser stack I suppose it was good idea. In my way there will be more exceptions, but they are not related to library itself.

Why I'm reporting here? So, I want ask a few questions.

  1. Why library using 'util'? Is it absolutely necessary?
  2. Do you need a more complicated report of using your library under react-native and common examples?

@kadamwhite
Copy link
Collaborator Author

Neither util nor url are in use within this project any longer. No special installation note should be needed.

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

No branches or pull requests

3 participants