# FAQ

#### What is the `editions` property inside `package.json`?

It is the property used to define the [Editions](https://editions.bevry.me/master) that the package provides.

#### Do I need to use the [Editions Autoloader](https://github.com/bevry/editions) to use editions?

No. You do not have to use the auto loader to use editions.

Editions can be considered in the following parts:

1. A standardised `editions` property inside your `package.json` file used for defining the editions a package provides
2. This standardised property can then be utilised by optional things due to its standardisation, such as an auto loader that can automatically include the correct edition for the current runtime, or renderers that render the available editions for the consumers awareness. These latter parts are entirely optional, and should not detract or distract from the promotion of the valuable by itself `editions` property.

#### Are there other ways of doing this without making use of editions?

Yes, but they are all terrible, hence why editions exists.

{% content-ref url="comparisons/alternative-approaches" %}
[alternative-approaches](https://editions.bevry.me/comparisons/alternative-approaches)
{% endcontent-ref %}

{% content-ref url="comparisons/comparison" %}
[comparison](https://editions.bevry.me/comparisons/comparison)
{% endcontent-ref %}

### How does the Editions Autoloader work?

Refer to the [Editions Autoloader API Documentation](http://master.editions.bevry.surge.sh/docs/global.html#requirePackage) as well as the [Editions Autoloader Changelog](https://github.com/bevry/editions/blob/master/HISTORY.md) for the most up to date information on its operation.

### How can I debug the auto loading process?

You can set the environment variable `EDITIONS_VERBOSE` to `yes`, this will output to stderr the relevant failure and stack trace for why editions are failing to load.


---

# Agent Instructions: 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:

```
GET https://editions.bevry.me/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.