Notion s3 url images can't be used about image HOT 4 OPEN

Before static generation or dev run, download all images to your public folder.

Yeah, I came up with a similar temporary solution in the end, but I wrote a custom Nuxt module to do this, using the Nitro hook nitro:prerender.

The module exports a custom event handler to be used in the API routes which returns which media needs to me downloaded (including videos) and the destination folder. Then, after the route is finished prerendering, it downloads all the media for that route.

It's available here to anyone which would like to take a look.

Until we have a way of hashing the urls to shorten them, I didn't come with a better solution

An alternative would be <NuxtImg/> providing an extra property to provide the saving path, so it would be possible to use the block UUID for example, like /notion-img/${block.id}.${extension}. But hashing would work as well.

from image.

Having the exact same issue with the same use-case from Notion.

I tried to circumvent the issue by creating a custom image provider which would call the get a block endpoint and then use it to short the image filenames to something like /notion/${blockId}, but even that can't be done at the moment since providers can't be async (#963).

I guess it would be better to have a proper provider for S3 temporary images, but the provider also accepting asynchronous calls would work as well. Locked into updating my site in this part for now :/

from image.

@Pijuli - I'm trying to do a similar thing with my own s3 buckets. Are you using a custom provider for this? Every time I try to call my s3 image path in the nuxt-img tag it prepends /ipx/ and breaks.

from image.

Having the exact same issue with the same use-case from Notion.

I tried to circumvent the issue by creating a custom image provider which would call the get a block endpoint and then use it to short the image filenames to something like /notion/${blockId}, but even that can't be done at the moment since providers can't be async (#963).

I guess it would be better to have a proper provider for S3 temporary images, but the provider also accepting asynchronous calls would work as well. Locked into updating my site in this part for now :/

There's another workaround I came with. It's not nice, it's not beautiful, but it works for now. Before static generatation or dev run, download all images to your public folder.
i.e. my package.json

{ "name": "my-web", "scripts": { "downloadNotionImg": "node src/notion.js", "start": "npm run downloadNotionImage && npm run dev", "build": "npm run downloadNotionImg && nuxi generate", } }

Then, save the file with the given name from notion, not the url. With that you already retrieved the image. Moving on. When parsing a block or whatever you need to parse, already in the render phase (or data retrieval), use the image name and the path from public, but not the s3 url. That way you have it locally accessed. You won't find the limit when creating the files as you are not using the url to do so.
I told you it's not pretty, but it works in my case. Theres a big table and a bunch of blocks. So not a big deal.

@smilburn1990 same same. You'll have to find a workaround that fits your needs as the one I explained

Until we have a way of hashing the urls to shorten them, I didn't come with a better solution. And I'm not that clever to be able to do a MR with a solution 🤷‍♀️

Have fun with the 255 chars limitation 😅

from image.