Plugins

Installing

npm install @nera-static/plugin-navigation

Any dependency whose name starts with @nera-static/ is discovered and applied automatically — no registration step.

The hook contract

A plugin is an ESM module exporting either or both hooks:

export function getAppData({ app, pagesData }) {
    return { ...app, myKey: 'value' }   // must return a plain object
}

export function getMetaData({ app, pagesData }) {
    return pagesData                    // must return an array
}

getAppData runs first; getMetaData sees the app it returned. Keep hooks synchronous — an async hook can wipe app on older generator versions.

Config lives in your project

Every plugin reads config/<name>.yaml from your site, not from the package. The YAML shipped inside the package is documentation; copy it into your config/ and edit. Missing keys fall back to sensible defaults.

Ordering

config/plugin-order.yaml controls execution order: names under start: run first, then everything else alphabetically, then names under end:. Search runs last so it indexes the final page data.

Templates

Plugins that ship views expose a publish command:

npx nera-navigation      # copies templates into views/vendor/plugin-navigation/

Then include them from your layouts. Publishing skips if the folder already exists — delete it (or pass --force) to pull in template updates.