nuxi generate does not create .output directory anymore

[dargmuesli]

Environment

• Nuxt version: 2.16.0-27358576.777a4b7f
• @nuxt/bridge version: 3.0.0-27495976.e31c604
• nitropack version: 0.2.5

Reproduction

As the linked, simple renovate-PR highlights the issue, I don't think another repro is needed. If it is, feel free to tell me.

Describe the bug

After upgrading @nuxt/bridge I receive the error FATAL [nitro] Please use nuxt generate for static target, which I (kinda) already do (nuxi generate).
Later on in the same build I now receive a webpack error originating from @nuxt/bridge, which I can "fix" by adding @nuxt/bridge to the build.transpile array.
After doing so tough, there is no .output directory created anymore.

Additional context

Sounds similar to nuxt/nuxt#13708.

Logs

https://github.com/dargmuesli/jonas-thelemann/runs/5992266520

[danielroe]

related: #31

[jegardiner]

I'm also having this problem, although I've not added @nuxt/bridge to the build.transpile array.

nuxi generate does not create the .ouput folder, despite mentioning it in it's success message:

✔ You can now deploy .output/public to any static hosting!

I can use nuxt generate, which outputs to the dist folder as a workaround for now.

[roseMix]

@jegardiner I was able to to use nuxt generate but only after adding "nuxt": "npm:nuxt-edge" to my package.json.

@danielroe is this intended behavior?

[dargmuesli]

The dist directory with nuxt generate does not contain the same files as the .output does with nuxi generate. My intention is to keep all files directly deployable to a static file hoster / nginx with nuxi, while what nuxt/dist gives me is a "server and client" output.

[roseMix]

@dargmuesli hmm did you set target: 'static' in nuxt.config.js? You're output in dist should then be uploadable to any static host.

BTW This is just a temporary workaround using the old nuxt command line. Hopefully once nuxt/framework#324 lands we'll be able to use the new nuxi command.

[dargmuesli]

Yes, I have target set to static.

[roseMix]

Rereading your question, for this workaround to work you need to change your package.json to "generate": "nuxt generate" using the old nuxt command.

Leaving it at nuxi generate tries to output the .output directory and fails because of the bug.

You might also need to add "nuxt": "npm:nuxt-edge" to devDependencies if you get errors about nuxt not being defined.

BTW as an aside, the Bridge Docs say to put the nuxi generate as the script for build not under generate not sure why.

[dargmuesli]

put the nuxi generate as the script for build not under generate not sure why.

I guess build is kind of the standard and for generated projects building is equivalent to generating.