Installing EmDash plugins: npm or the registry?
Understand the installation routes, check prerequisites and install the right plugin for your EmDash project.
Installation method and execution format are different
An EmDash plugin can be installed through the administration registry or managed as an npm dependency. Do not assume that every npm package is native: a configuration-managed plugin may also be sandboxed. Read the publisher’s instructions before choosing where it belongs.
For Sneaps, the distinction is straightforward: Image Generator has a registry listing, while Import/Export is a native npm plugin. Your choice starts with the tool you need, then its documented installation method. Trying to install a native package as a sandboxed bundle will not give it the required environment.
Use the registry when the plugin supports it
For a registry plugin, review its listing, publisher, requested permissions and instructions. The administration needs a configured sandbox runner, bundle storage and an administrator allowed to manage plugins. A visible catalogue does not by itself prove that installation is configured.
On a client project, record why the plugin is being added and who will maintain it. Check behaviour on a staging environment before making it part of a critical publishing workflow. A sandbox limits execution, but you still need to understand the permissions you approve.
Use npm for a native site dependency
Install the package in the Astro project and register its exported factory as documented. For Import/Export, import importExport from @sneaps/import-export and add importExport() to the existing plugins array. Keep other plugins rather than replacing the entire array with a copied example.
Commit the dependency and lockfile changes in your site project, build and redeploy. Confirm that the expected administration entry appears and test with a small dataset. Native plugin maintenance belongs to the project’s development and deployment workflow, rather than a one-click admin installation.
Import/Export installationCheck the platform before troubleshooting the package
If installation fails, first determine whether the failure happens before the plugin runs. Check your EmDash version, hosting environment, configuration and administrator access. Consult the current sandbox setup guide for the platform-specific runner and bindings.
Then check the package name and the export you registered. Do not invent a factory name from the npm package name. Capture the exact error and compare it with the documentation. Changing credentials or repeatedly redeploying unrelated configuration will not help if the plugin was registered in the wrong place.
Plan updates and removal from the start
Keep a record of the installed version and the feature it provides. Before an update, export or back up relevant data, read release notes and verify the result away from production. Check permission changes as carefully as new features.
Before removal, find out whether the plugin owns stored data or whether its output is used by templates. Removing a dependency may require configuration changes and a deploy; removing a registry plugin follows its administration workflow. Document a rollback route that your team can actually carry out.
Pick the tool that matches the task
For generated featured images, start with Image Generator. For moving collection content with structured files, use Import/Export. Both extend EmDash, but their installation and operational needs differ.
A good plugin choice has a clear job, documented compatibility and an owner responsible for updates. Install only what the site needs today, then add other tools when a concrete editorial or business need appears. That keeps troubleshooting and handover understandable for the next person maintaining the project.
Image generation guide