Nuxt.js: Remove asyncData for full static export

Created on 19 May 2020 · 4Comments · Source: nuxt/nuxt.js

Version

Reproduction link

Steps to reproduce

Switch to nuxt-edge on any nuxt project
Enable target: static
Build and export it

What is expected ?

Nuxt should export the static site with asyncData removed. It isn't needed for static export (payload.js is used instead) => unnecessary data for the user to download.

What is actually happening?

Nuxt keeps asyncData.

_{This bug report is available on Nuxt community (#c10677)}

bug-report

Source

J05HI

All 4 comments

It is still necessary for the following situations:

In case the payload can't be fetched
When using SPA fallback (no payload in this case)
When using preview mode

manniL on 20 May 2020

Hello @manniL

thank you for your reply! I've some questions.

In case the payload can't be fetched

When can't the payload be fetched? If the user lacks of network access? The API would be unavailable, too.

When using SPA fallback (no payload in this case)

Isn't the full static export a static site which hydrates to a SPA without API requests? => we don't need asyncData.

When using preview mode

What do you mean with "preview mode"? Running Nuxt in dev?

J05HI on 20 May 2020

When can't the payload be fetched? If the user lacks of network access? The API would be unavailable, too.

The most common situation I can think of is when using the SPA fallback (as there won't be a payload). But there might be other scenarios where this comes in handy instead of letting the site break.

When using SPA fallback (no payload in this case)
Isn't the full static export a static site which hydrates to a SPA without API requests? => we don't need asyncData.

Yes, this is correct so far. But you can exclude routes from being generated (e.g. everything behind authentication). Those have no payload but can still be accessed "normally" and will load as "SPA" (no generated HTML)