Patrick Heneise

I created the release v0.2.0 from the latest master. Unfortunately I don’t have access to npm and can’t complete the semantic-release setup for automated publishing. https://github.com/xdamman/mediumexporter/releases/tag/v0.2.0

Thanks for reporting this! Can you post a URL of a specific page that returns these errors? I imported pages with inline code and had no issues.

I don't have access to npm to publish the new version, but I'll see what I can do.

Is the `author` required? I've added all other fields in https://github.com/xdamman/mediumexporter/pull/14 and can add the "Originally published" note as well.

Ok. I supposed this is no longer relevant, but I'll have a look. I'm optimising for @gohugoio support at the moment, which is almost the same.

No, SASL buckets are not supported yet.

Yeah, ipx/sharp as optional dependency for local/development and opting out on production would be great. If you point me in the direction on how this can be implemented, I can...

Thanks. I'll open a PR soon.

Unfortunately this didn't fix the issue. As we're throwing an Error, the build fails when packages are installed with `-no-optional` ``` Step #1: ERROR [@nuxt/image] ipx is an optional dependency...

We're not using Vercel. ``` image: { domains: ['https://XYZ'], provider: 'cloudflare', providers: { cloudflare: { provider: '~/providers/cloudflareImageProvider', options: { baseURL: 'https://images.XYZ.workers.dev' } } } }, ``` The error throws straight...