Alexandre BODIN 61c0c9d9b4
Add v3.x and remove alpha docs (#6344)
Signed-off-by: Alexandre Bodin <bodin.alex@gmail.com>
2020-05-25 18:11:45 +02:00

91 lines
2.0 KiB
Markdown

# Hooks
The hooks are modules that add functionality to the core. They are loaded during the server boot.
## Structure
### File structure
```js
module.exports = strapi => {
const hook = {
/**
* Default options
*/
defaults: {
// config object
},
/**
* Initialize the hook
*/
async initialize() {
// await someAsyncCode()
// const settings = {...this.defaults, ...strapi.config.hook.settings.**};
},
};
return hook;
};
```
- `defaults` (object): Contains the default configurations.
- `initialize` (function): Called during the server boot.
The [configurations](#configuration-and-activation) of the hook are accessible through `strapi.config.hook.settings.**`.
The hooks are accessible through the `strapi.hook` variable.
### Node modules
Every folder that follows this name pattern `strapi-hook-*` in your `./node_modules` folder will be loaded as a hook.
A hook needs to follow the structure below:
```
/strapi-hook-[...]
└─── lib
- index.js
- LICENSE.md
- package.json
- README.md
```
The `index.js` is the entry point to your hook. It should look like the example above.
### Custom hooks
The framework allows to load hooks from the project directly without having to install them from npm. It's a great way to take advantage of the features of the hooks system for code that doesn't need to be shared between apps. To achieve this, you have to create a `./hooks` folder at the root of your project and put the hooks into it.
```
/project
└─── admin
└─── api
└─── config
└─── hooks
│ └─── strapi-documentation
│ - index.js
│ └─── strapi-server-side-rendering
│ - index.js
└─── public
- favicon.ico
- package.json
- server.js
```
## Configuration and activation
To activate and configure your hook with custom options, you need to edit your `./config/hook.js` file in your Strapi app.
```js
module.exports = {
settings: {
'hook-name': {
enabled: true,
},
},
};
```