remotion-dev/remotion · error · Error

No published version is known for ${name}

Error message

No published version is known for ${name}

What it means

When Browser Studio downloads a portable project, getPublishedVersion resolves each dependency's version from a dependencyVersions map, falling back to the 'remotion' key for @remotion/* packages. If neither the package's own entry nor the remotion fallback yields a version, it throws because it cannot emit a valid package.json dependency range.

Source

Thrown at packages/browser-studio/src/download-project.ts:101

const getPublicFileArchivePath = (path: string) => {
	const relativePath = path.startsWith('/') ? path.slice(1) : path;
	return `public/${validateRelativePath(relativePath)}`;
};

const getPublishedVersion = ({
	name,
	dependencyVersions,
}: {
	name: string;
	dependencyVersions: Record<string, string>;
}) => {
	const version =
		dependencyVersions[name] ??
		(name.startsWith('@remotion/') ? dependencyVersions.remotion : null);

	if (!version) {
		throw new Error(`No published version is known for ${name}`);
	}

	return version;
};

const resolvePortableDependencySpec = ({
	dependencyVersions,
	name,
	spec,
}: {
	dependencyVersions: Record<string, string>;
	name: string;
	spec: string;
}) => {
	if (spec === 'catalog:') {
		return getPublishedVersion({name, dependencyVersions});
	}

View on GitHub (pinned to 78fe4bb3fd)

Solutions

1. Ensure every dependency in the project is represented in the dependencyVersions map passed to the download flow.
2. For @remotion/* packages, ensure a 'remotion' version is present in the map (it is used as fallback).
3. Avoid non-published, local, or git-based dependencies in portable Browser Studio projects.
4. Regenerate the dependencyVersions metadata after adding or upgrading a package.

Example fix

// before
// dependencyVersions = { 'react': '19.0.0' }  // project also uses 'lodash'

// after
// dependencyVersions = { 'react': '19.0.0', 'lodash': '4.17.21', 'remotion': '4.0.0' }

const assertVersionKnown = (name: string, dependencyVersions: Record<string, string>) => {
  const known = dependencyVersions[name] ??
    (name.startsWith('@remotion/') ? dependencyVersions.remotion : undefined);
  if (!known) {
    throw new Error(`No published version known for ${name}; add it to dependencyVersions`);
  }
};
// validate every project dependency before calling download

const isVersionKnown = (name: string, dv: Record<string, string>): boolean =>
  !!dv[name] || (!!dv.remotion && name.startsWith('@remotion/'));

When it happens

Trigger: The project depends on a package not present in dependencyVersions, or an @remotion/* package when the map has no 'remotion' key. Reproduced by adding a dependency the downloader was not given version metadata for.

Common situations: Adding a new dependency to the project without updating the dependencyVersions metadata; an unknown/non-published package; @remotion/* sub-package used while the remotion version is unknown; custom/local deps that have no published version.

Related errors

• The repository package ${packageName} does not expose ${subp
• Invalid public file path: ${path}
• ${oldRelativePath} does not exist
• ${newRelativePath} already exists
• Could not find "react-dom" package. Did you install it?

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