> For the complete documentation index, see [llms.txt](https://kvision.gitbook.io/kvision-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kvision.gitbook.io/kvision-guide/4.-integrating-with-javascript-libraries.md).

# 4. Integrating With Javascript Libraries

You're in a safe space, and we know how you probably feel about Javascript. That said, there are thousands of great Javascript (and Typescript) libraries out there which can accelerate your application's development. While KVision doesn't provide much in the way of specific functionality for integrating libraries, this chapter exists to keep this guide as comprehensive as we can make it.

Several chapters of the kotlinjs docs are worth attention when integrating with libraries:

* <https://kotlinlang.org/docs/js-interop.html>
* <https://kotlinlang.org/docs/dynamic-type.html>
* <https://kotlinlang.org/docs/using-packages-from-npm.html>
* <https://kotlinlang.org/docs/js-modules.html>

This chapter is very much a work in progress, but we'll build on this material to help you integrate with a wide variety of third party libraries.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kvision.gitbook.io/kvision-guide/4.-integrating-with-javascript-libraries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.