I'm fighting with

StaticSite

and must be missing something. All I've done is set up the default SST project (

npx create-serverless-stack@latest blah

), created the default Nuxt project in the root of that (

npx create-nuxt-app frontend

), and then modified MyStack.js to tell

StaticSite

how to build the Nuxt app and where to find the static files. Easy. An

npx sst start

works but deploys an SST place-holder site which recommends doing an

npx sst deploy

. So I do that and visit the CloudFront link spat out by the deploy. I get an access denied error expressed as an XML document.

Hey @Mark Fox can you double check if the

buildOutput

is pointing to the right folder?

The contents of the bucket on S3 sure don't include what I would expect. So here's what I have:

const site = new sst.StaticSite(this, "Nuxt Site", {
      path: "frontend",
      buildOutput: "dist",
      buildCommand: "npm run generate",
      errorPage: StaticSiteErrorOptions.REDIRECT_TO_INDEX_PAGE,
    });

    this.addOutputs({
      "CloudFront URL": site.url,
    })

./blah

is the project,

./blah/frontend

is the Nuxt frontend, and

./blah/frontend/dist

should be the

buildOutput

, right?

What’s in the

./blah/frontend/dist

page?

./blah/frontend/dist

contains the

_nuxt

and

inspire

folders,

.nojekyll

,

200.html

,

favicon.ico

, `index.htm`l,

v.png

, and

vuetify-logo.svg

. Just as one would expect after doing

npx nuxt-init blah; cd blah; npm run generate

. So the buildCommand and buildOutput seem to be correct.

Hey @Mark Fox, that’s really weird. Do you want to share your repo and maybe I can give it a try on my end?

Sure.