+esm version of library no longer available for rita package about jsdelivr HOT 7 OPEN

The link works again because I reverted package.json to the old entries in version 3.0.27. When I use the new entries, that file disappears. Can you describe what triggers the creation of the file via rollup/terser ?

from jsdelivr.

Indeed, I can see the problem with 3.0.26. Will take a look.

from jsdelivr.

The resolver fails with the error Error: Default condition should be last one, see docs:

"default" - the generic fallback that always matches. Can be a CommonJS or ES module file. This condition should always come last.

It should work if you move types to be before default.

from jsdelivr.

The error logs are not public, unfortunately. In most error cases, the response itself indicates the reason, but resolver errors are not so clear, that's something we might improve in the feature.

In this specific case, if you want to make sure it'll work after that change, a beta release might be a good option. 3.0.28-beta will be ignored for our "latest" link https://cdn.jsdelivr.net/npm/rita/+esm but you can still access it directly via https://cdn.jsdelivr.net/npm/[email protected]...

from jsdelivr.

This particular change should no break anything, and the posted link works for me:

from jsdelivr.

This may indeed solve the specific issue (I'm hesitant to try because I don't want to again break work for downstream users), but the larger problem is that this failure is opaque to the me as library maintainer. I suppose I would need to integrate specific tests of the jsdelivr urls into my build process... But on a failure, where would I find the resolver logs you refer to for debugging ?

from jsdelivr.

Would be ideal if the resolver error could be passed to the generated file

from jsdelivr.