> For the complete documentation index, see [llms.txt](https://aurelia-1.gitbook.io/v1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aurelia-1.gitbook.io/v1-docs/aurelia-packages/store.md). # Store ### Introduction The Aurelia Store plugin provides a robust and flexible solution for managing state in your Aurelia applications. It is built upon the solid foundation of RxJS, leveraging the power of `Observables` and `BehaviorSubject` to create a reactive and predictable state management system. While you don't need to be an RxJS expert to use the Aurelia Store, having a basic understanding of these concepts can be beneficial. In essence, `Observables` represent a stream of data that can be observed over time, while a `BehaviorSubject` is a special type of `Observable` that holds a current value and emits it to new subscribers. ### Getting started To begin using the Aurelia Store plugin, you first need to install it via npm: ```bash npm install aurelia-store ``` **Note:** If you are not already using RxJS in your project, it's recommended to install it as a project dependency: ```bash npm install rxjs ``` This ensures that you have the latest version of RxJS and that it's properly integrated into your project. --- # 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://aurelia-1.gitbook.io/v1-docs/aurelia-packages/store.md?ask=&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.