Benedikt Rötsch

Did you try it with plain npm? Looks like you used pnpm? The relevant line is here: https://github.com/axe312ger/sqip/blob/master/packages/sqip/src/sqip.ts#L142 Maybe output the actual error message before the throw and share it...

Really weird. In the end we do a "regular await import" and if that fails, we throw. Not like this is super fancy or rare code. 🤔 I can try...

So strange and annoying that the module resolution is failing so badly. I am happy about any help, I'll try to add official NextJS support later this year For now.....

Yay, can't wait for it!

Push! This is important! @wdullaer

Maybe also consider update the other dependencies. This module is pretty small and simple, nothing should break.

Yes something is off. There are types but my TS (5) complains about no types existing :( Edit: My quick and dirty hack... I copied the file `node_modules/xss/typings/xss.d.ts` to my...

you just pushed a new version, are you planning to come back?

Rebased it on master in `feat/verbose` and released it as canary release. Check `npm i gatsby-plugin-netlify-cache@canary` and let me know :)

That might be an option. We might also rerun the build to check if it actually did speed up 🤔