hosnas
hosnas
@dc7290 Because we use some of the things that aren't supported with next export. And still we want to optimize the images in the build time. so that we can...
yes @dc7290 I want to use next/image with that config, and only want to show user the optimized image. I dont need lazy load and placeholders.
@dc7290 My problem was if I want to use `export const config = { unstable_runtimeJS: false, };` The default image API doesn't work at all. So I thought maybe it...
@DirtyF can you elaborate a little more? you mean with small tweaks we can support collections too?
Supporting collection is easy. I can submit a PR for it. However there is [a conflict](https://github.com/jekyll/jekyll/issues/6410) with the way Jekyll currently handles files inside collections, that needs to be addressed...
@nhoizey @DirtyF Is the plugin compatible anymore? specially with regard to [this PR](https://github.com/jekyll/jekyll/pull/6685)? I think this plugin needs an update to support post and collections the same way.
@ashmaroli I still have this error when I want to sort documents with pagination-v2 plugin. cc: @sverrirs
When we can have this interesting feature?
@keyvan-m-sadeghi can confirm it works as intended. Great job @Arvant and @sampathBlam :+1: I just want to say its worth mentioning it in the readme doc.
Any update for this issue? Can we assume it is coming soon? I am desperately waiting for it.