> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/migrating-to-aurelia-2/migrating-to-aurelia-2/for-plugin-authors.md).

# For plugin authors

Aurelia 1 was released in 2015. In the years that have passed, an ecosystem of user-created libraries and plugins has been created. If you are a plugin author of a v1 plugin or looking to port over a plugin to v2, this is the section you are looking for.

Before proceeding, you should read through [the parent section](/migrating-to-aurelia-2/migrating-to-aurelia-2.md) to understand the differences between v1 and v2.

In Aurelia 2, the `plugin` method you called in v1 is no more. Plugins in Aurelia 2 are no different to components and other resources. You pass them to the `register` method inside your bootstrap code to load them.

There are numerous ways you can create Aurelia 2 plugins or port over v1 plugins. However, the easiest reference point is to look at how other plugins have been ported over to Aurelia 2.

Please keep in mind these are third-party plugins, and the Aurelia team claims no responsibility for the quality and safety of the code. Use them as a reference point for your own Aurelia 2 plugins, but use precaution.

* [Cardigan UI](https://github.com/Vheissu/au-cardigan-ui)
* [Aurelia 2 Table](https://github.com/Vheissu/aurelia2-table)
* [Aurelia 2 Auth](https://github.com/Vheissu/aurelia2-auth)
* [Aurelia 2 Google Maps](https://github.com/Vheissu/aurelia2-google-maps)


---

# 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.aurelia.io/migrating-to-aurelia-2/migrating-to-aurelia-2/for-plugin-authors.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.