See unpkg.com's listing - although the directory exists in source (a bad practice, but I won't get into it here), the published package does not include it.
This is potentially an issue for bundlers, as the package.json lists es/index.js as the module entrypoint - either they will error or not be able to do as good tree-shaking.
To be frank, I have no idea why it's missing from the bundle - the directory existed when it was packaged, .npmignore is empty and the package.json doesn't have a files entry: which is what is listed here as the reasons it might be missing. Is there something funky in the packaging workflow that could be deleting it before npm pack/publish?
Note: For what it's worth, the folder is only missing starting v2.0.2
This breaks our tests. Would love to see this fixed.
@simonbuchan So we meet again :)
@simonbuchan sorry about that. We will publish a new version to fix it.
Closing as this should have been fixed in the latest version of Cognito.