You're reading docs for Nextly Alpha. APIs may change between releases.

CLIError codes

PLUGIN_ENTRY_UNNAMED

The file given to `--plugin` exports no plugin definition with a name.

Cause

The file given to --plugin exports no plugin definition with a name.

A plugin's migrations are recorded under its name, so the definition --plugin reads must have one.

Fix

Point --plugin at the file that exports the plugin, made with definePlugin and given a name.

Example

✗ The plugin entry src/plugin.ts exports no definition with a name, so its migrations cannot be attributed.
  Why:  A plugin's migrations are recorded under its name.
  Next: Point `--plugin` at the file that exports the plugin, made with `definePlugin` and given a `name`.
  Docs: https://nextlyhq.com/docs/cli/errors/plugin-entry-unnamed  (PLUGIN_ENTRY_UNNAMED)

On this page

Was this page helpful?