remotion-dev/remotion · error · Error

The following packages are not Remotion packages: ${invalidP

Error message

The following packages are not Remotion packages: ${invalidPackages.join(', ')}. Must be one of the Remotion packages or one of the supported extra packages: ${Object.keys(EXTRA_PACKAGES).join(', ')}.

What it means

`addCommand` filters the requested package names against `listOfRemotionPackages` and the `EXTRA_PACKAGES` map. Any name in neither set is collected into `invalidPackages`, and if any exist, the command aborts listing both the invalid names and the supported extra packages. This prevents installing arbitrary/typo'd package names under the Remotion installer.

Source

Thrown at packages/cli/src/add.ts:43

export const addCommand = async ({
	remotionRoot,
	packageManager,
	packageNames,
	logLevel,
	args,
}: {
	remotionRoot: string;
	packageManager: string | undefined;
	packageNames: string[];
	logLevel: LogLevel;
	args: string[];
}) => {
	// Validate that all package names are Remotion packages
	const invalidPackages = packageNames.filter(
		(pkg) => !listOfRemotionPackages.includes(pkg) && !EXTRA_PACKAGES[pkg],
	);
	if (invalidPackages.length > 0) {
		throw new Error(
			`The following packages are not Remotion packages: ${invalidPackages.join(', ')}. Must be one of the Remotion packages or one of the supported extra packages: ${Object.keys(EXTRA_PACKAGES).join(', ')}.`,
		);
	}

	const {
		dependencies,
		devDependencies,
		optionalDependencies,
		peerDependencies,
	} = StudioServerInternals.getInstalledDependencies(remotionRoot);

	// Check if packages are already installed
	const allDeps = [
		...dependencies,
		...devDependencies,
		...optionalDependencies,
		...peerDependencies,
	];

View on GitHub (pinned to 78fe4bb3fd)

Solutions

Check the spelling against `listOfRemotionPackages` (e.g. @remotion/shapes, @remotion/motion-blur).
Use `EXTRA_PACKAGES` entries only — the error lists the supported extras.
Install non-Remotion packages with your package manager (npm/yarn/bun) directly.
Upgrade the Remotion CLI if the package was added in a newer version.

Example fix

// before
npx remotion add @remotion/shape

// after
npx remotion add @remotion/shapes

Defensive patterns

Strategy: validation

Validate before calling

import {listOfRemotionPackages} from '@remotion/cli/list-of-remotion-packages';
import {EXTRA_PACKAGES} from '@remotion/cli/extra-packages';
function isValidAddTarget(pkg: string): boolean {
  return listOfRemotionPackages.includes(pkg) || !!EXTRA_PACKAGES[pkg];
}

Type guard

const isAddablePackage = (pkg: string): boolean =>
  listOfRemotionPackages.includes(pkg) || !!EXTRA_PACKAGES[pkg];

Try / catch

try { await addCommand({...}); }
catch (e) {
  if (e instanceof Error && /not Remotion packages/.test(e.message)) {
    // prompt user to correct the name; do not auto-retry.
  }
}

Prevention

Check package spelling against the Remotion package list.
Use the package manager directly for non-Remotion packages.
Upgrade the CLI if the package is newer than your CLI version.

When it happens

Trigger: Running `npx remotion add <pkg>` with a package name that is not a Remotion package and not in EXTRA_PACKAGES; typos like '@remotion/shape' (missing 's'); requesting a package that was renamed or does not exist.

Common situations: Misspelling a package name; requesting a third-party package via `remotion add` instead of the package manager; version mismatch where a package exists in newer Remotion but not the installed CLI.

Related errors

AI-assisted analysis of remotion-dev/remotion@78fe4bb3fd (2026-08-12). Data as JSON: /api/errors/c82a4fc014f006ff. Report an issue: GitHub.