> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/android/get-started/faq/react-native-use.md).

# How do I use Apryse React Native with TypeScript?

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

Our library has support for JavaScript as well as TypeScript. To use our library with either language, follow these [installation instructions](https://github.com/ApryseSDK/pdftron-react-native#installation).

For existing users:

* If you already use TypeScript, simply update your `react-native-pdftron` dependency to version 3.0.0 or higher to gain access to our typings.
* If you want to migrate to TypeScript, see [Adding TypeScript to an Existing Project](https://reactnative.dev/docs/next/typescript#adding-typescript-to-an-existing-project).
* If you do not use TypeScript and don't want to, you can continue to use and update our library as before. Updating to version 3.0.0 will not automatically download TypeScript as a dependency.

Note: TypeScript version 3.4.1+ is recommended. Although compilation still works with lower versions, typings may degrade to `any`.

For more information, see our [TypeScript section](https://github.com/ApryseSDK/pdftron-react-native#typescript).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.apryse.com/android/get-started/faq/react-native-use.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.