> For the complete documentation index, see [llms.txt](https://docs.pandium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript.md).

# Write the Integration in Typescript

Write a TypeScript “Pokémon of the Day” integration for Pandium by customizing the starter repo, updating package settings, installing dependencies, and building before each run.

Beginning with the starter files created by Pandium, you will now write your Pokémon of the day integration and get it working locally!

Since you just pulled Pandium's initial commit your new integration folder should have a the following file structure:

<pre><code><strong>├── src
</strong>  └── index.ts
  └── lib.ts
└── package.json
└── PANDIUM.yaml
└── tsconfig.json
</code></pre>

Start by replacing the pre-filled generic information with something that fits our project.

1. In the package.json change the name from `pokemon` to `pokemon-of-the-day`.

You may notice the start command is `node/build/src` and doesn't mention `ts-node`. That's because this TypeScript integration is a module. You can read more about [TypeScript Modules](https://www.typescriptlang.org/docs/handbook/modules/introduction.html) if you haven't written one before, but for our integration's purposes it means:

* You will need to build before any code changes you've made will take effect.
* Your imports will need to reference .js files.

1. Run `pandium local build`. This executes the `build` command from your PANDIUM.yaml, which installs the dependencies and compiles the TypeScript, so it should add the node\_modules and build folders to your root directory. You will run this before every local run of the integration.


---

# 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.pandium.com/getting-started/pandium-integration-tutorial/pokemon-of-the-day-part-1/write-the-integration-in-typescript.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.