How to Fix "Unable to Resolve Package" Error in Framer

If you work with custom code in Framer, you might have seen the “Unable to resolve package” error. This usually happens when a dependency or version mismatch prevents Framer from loading an NPM package correctly. In this guide, I’ll explain why it happens and how to fix it quickly.

Currently, Framer doesn't have a native way to manage dependencies. You can track the progress of this feature by following the feature request.

Why This Error Happens

Framer uses JSPM to handle NPM packages. JSPM converts them into ES Modules so browsers can use them directly.

The problem is that not all packages work perfectly in browser environments. Some rely on Node.js features or dependencies that cannot be converted cleanly. In other cases, version conflicts between dependencies can cause the “Unable to resolve package” message.

Why Packages Do Not Update Automatically

When you first import a package, Framer saves its version along with its dependencies. These versions do not update automatically. This helps prevent unexpected breaking changes but can cause problems when older versions become incompatible.

If your project relies on older overrides or components, it might need a manual update to fix the issue.

How to Import Packages Manually with a Specific Version

A good workaround is to import packages directly from a CDN that lets you specify the version manually, such as esm.sh.

Instead of importing a package like this:

import confetti from "canvas-confetti"

You can import it with a version number like this:

import confetti from "<https://esm.sh/canvas-confetti@1.6.0>"

This method gives you more control over which version Framer loads and often helps bypass version mismatches.

⚠️ Note: Packages that depend directly on React may still not work correctly when imported via CDN.

Final Tip

This method will fix most dependency issues, but not all of them. If you keep seeing the same error, check whether the package you are using supports browser environments.

You can also ask for help in the Framer community support. Many developers share similar experiences and quick fixes there.