> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-admin/10.2-admin/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp/creating-a-visualization-visapi/creating-the-pentaho-web-package-visapi-custom-visualization-creation.md).

# Create the Pentaho web package

In [Develop a visualization in a sandbox](/pdia-admin/10.2-admin/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp/creating-a-visualization-visapi/walk-through-tutorial-cp-visapi.md), you developed a custom visualization and tested it in a controlled sandbox environment.

Excluding the sandbox-specific files, you can package the following files and the `css` folder:

* `package.json`
* `Model.js`
* `View.js`
* `clickD3.js`
* `config.js`

Any runtime client-side dependencies must also be provided to the platform. In the case of this tutorial, the only runtime dependency is the D3 library. The `@pentaho/visual-sandbox` is a development-time dependency. Dependencies can be provided separately in their own package or bundled together with your visualization. For packaging the tutorial visualization, you just need to ZIP your files and runtime dependencies. Do not include temporary files and development-time dependencies.

By using the `npm pack` command, you can ensure only your files and bundled dependencies are compressed in the resulting TGZ file, as shown in the following example:

```
# Package your files.
npm pack
```

With the web package in place, you can now deploy it. See [Deploying a visualization](/pdia-admin/10.2-admin/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp/deploying-a-visualization-cp-visapi.md) for further instructions.


---

# 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.pentaho.com/pdia-admin/10.2-admin/pentaho-developer-center-overview-cp/platform-javascript-apis/visualization-api-cp/creating-a-visualization-visapi/creating-the-pentaho-web-package-visapi-custom-visualization-creation.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.