Support for ssr: false

[dladeira]

I am trying to use nuxt-img with electron, but the problem is that electron does not working with ssr, and it seems that this module does not work without server-side rendering (ssr: true).

Is there planned support for ssr: false. Before, in version v0 there seemed to be a static provider (docs), does something like this exist in this version? Where maybe some of the nuxt-img features are dropped, but the images still work with the ssr: false property?

Context, when running with ssr: false ipx does not run, meaning the _ipx folder does not exist, see this issue.

--

The documentation is also rather confusing, from static images

In that case, you can tell Nuxt to pre-render images by using the nitro.prerender.routes option

What does this mean, do I have to loop through all my images, and create an array with a prefix of /_ipx/w_???.

[Baroshem]

@danielroe is this feature somewhere on the roadmap? :)

[danielroe]

ssr: false means no HTML rendering of your Vue pages and this is not compatible with prerendering a totally static website with image optimisation. nuxt would be unable to know what images to optimise.

(it would work fine if you had a server at runtime)

however, you can statically generate a site without ssr: false. this should work fine. normally using ssr: false when prerendering is a mistake or misunderstanding of how nuxt does ssg.

[dladeira]

Could generate the optimized images during generation, and then serve them statically? Or perhaps at least make it so the images do load, but there isn't any processing by nuxt-img so the site doesn't break?

[danielroe]

that’s exactly what ipxStatic does. but it requires you to have ssr: true turned on during static generation.

to reiterate, ssr: true does not mean you have a server at runtime

[dladeira]

Isn't the whole point of SSR that you have a server at runtime that helps with page rendering? I'm getting that impression from this universal rendering in the wiki

Cost: A server needs to be running in order to render pages on the fly. This adds a monthly cost like any traditional server. However, the server calls are highly reduced thanks to universal rendering with the browser taking over on client-side navigation. A cost reduction is possible by leveraging edge-side-rendering.

[danielroe]

I'm not sure I understand the point you are making.

You can statically render all your pages without any server at runtime. You need ssr: true to benefit from most of the benefits of this, like SEO or image optimisation. Only very rarely would it ever be correct to use ssr: false with a fully static site. (Possibly in the case of an electron app, like your situation.)

You can also have a server running at runtime. Mostly I would also recommend ssr: true but in the edge case of opting for ssr: false the main benefit you would get is having API routes, like /_ipx.

[dladeira]

My apologies I'm a bit confused. What is the point of ssr: true, if you don't need to have a server running at runtime? What exactly does it do?

ssr: false means no HTML rendering of your Vue pages and this is not compatible with prerendering a totally static website with image optimisation. nuxt would be unable to know what images to optimise.

Could we not optimize the images, just serve them, so the website doesn't break? Maybe let the users know with a warning that the images aren't being optimized?