popmotion 11.0.3 import not working (missing exports)

[m0dch3n]

Problem

Module '"popmotion"' has no exported member 'listen'.ts(2305

How to reproduce

npm i popmotion@11.0.3

Then in my .ts file

import { listen } from 'popmotion'

Expected behaviour

I took the example here

Either this documentation is not up to date, or there is a bug...

Btw tween and some others are also not working...

[amish1211]

At the site "https://popmotion.io/learn/install/" it's told to use "https://unpkg.com/popmotion@11.0.3/dist/popmotion.global.min.js" as the script tag's src value. But it seems that because there's no file named "popmotion.global.min.js" on "https://unpkg.com/popmotion@11.0.3/dists" so it's not able to load the needed js and hence nothing is working as expected.
Popmotion please have a look and provide the correct link

[stokesman]

For now, probably every page on popmotion.io that isn't at the domain root dates from the days of version 8. So if you want to follow any of those examples you'll have to either:
npm i popmotion@8

or for unpkg:
https://unpkg.com/popmotion@8/dist/popmotion.global.min.js

[marc-wilson]

Is this project dead? The documentation seems to be inaccurate, GitHub issues aren't getting any responses and there haven't been any updates pushed for a year.

[maximilliangeorge]

I think @mattgperry spends his efforts on https://motion.dev nowadays.

I agree the whole popmotion ecosystem is a very confusing – there's Popmotion Pure (which is popmotion v8), reachable from https://popmotion.io/learn. This version has a very different API and approach than the later versions (https://popmotion.io). Both show up on Google when you search for Popmotion, and it's easy to get them mixed up.

It would make sense to split these into separate npm packages, and to create a clearar naming distinction between them. This ecosystem is such a gold mine, but unfortunately a bit difficult to navigate unless you've been around for a while.