Skip to content

Commit

Permalink
[Docs] Linking Libraries fix site->side, prefer only to just
Browse files Browse the repository at this point in the history
  • Loading branch information
Brent Vatne committed May 18, 2015
1 parent d63eac4 commit 424d131
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions docs/LinkingLibraries.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ For most of the libs it will be as simple as dragging two files, sometimes a thi
step will be necessary, but no more than that.

_All the libraries we ship with React Native live on the `Libraries` folder in
the root of the repository. Some of them are pure JavaScript, and you just need
the root of the repository. Some of them are pure JavaScript, and you only need
to `require` it. Other libraries also rely on some native code, in that case
you'll have to add these files to your app, otherwise the app will throw an
error as soon as you try to use the library._
Expand Down Expand Up @@ -47,9 +47,8 @@ Not every library will need this step, what you need to consider is:

_Do I need to know the contents of the library at compile time?_

What that means is, are you using this library on the native site or just in
JavaScript? If you are just using it in JavaScript, you are good to go!

What that means is, are you using this library on the native side or only in
JavaScript? If you are only using it in JavaScript, you are good to go!

This step is not necessary for libraries that we ship with React Native with the
exception of `PushNotificationIOS` and `LinkingIOS`.
Expand Down

0 comments on commit 424d131

Please sign in to comment.