tombu Posts - Answer Overflow

tombu

•Created by tombu on 9/10/2024 in #❓・help

How can I include a comment that doesn't get stripped out in a production build?

Ideally my comment would go in <head> somewhere but it would also work if it was inside app.vue, so within <div id="__nuxt">. I'm deploying a static generated site using pnpm generate. I've tried looking through Nuxt, Vue and Vite docs but haven't found anything.

1 replies

NNuxt

•Created by tombu on 7/17/2024 in #❓・help

404 error handling acting strangely

I'm developing my first Nuxt 3 site and I'm experiencing an issue I'm not used to from v2. I'm trying to throw an error on a slug page after useAsyncData, either if throwAsyncData returns an error, or if the data it returns has no value. It works great on a slug page - if I navigate to it directly or if I refresh it - but if I try to navigate to the slug-with-no-data using a <nuxt-link> from elsewhere in the app, rather than navigating to the slug page and showing the error, the address bar updates to show the slug-with-no-data url, nothing happens on the front-end and I get Uncaught (in promise) Error: Page Not Found in the console. What can I do to easily handle the error so that it just shows the same 404 as if I visited the slug page directly? Here's my createError

const {
    data: service,
    error
} = await useAsyncData(
…

if (error.value ||
    !service.value) {
    throw createError({
        statusCode: 404,
        statusMessage: 'Page Not Found'
    });
}

const {
    data: service,
    error
} = await useAsyncData(
…

if (error.value ||
    !service.value) {
    throw createError({
        statusCode: 404,
        statusMessage: 'Page Not Found'
    });
}

Edit: I've found the magic fatal: true option that seems to do what I want, I'm still interested to know if that's the best way though!

1 replies

Gaming

Programming