nuxt: Nuxt Programmatic: Renderer is loaded but not all resources are unavailable! Please check ...
Version
Reproduction link
Steps to reproduce
Hey, bare server and running into this issue when running nuxt programmatically:
server.js
const { Nuxt, Builder } = require('nuxt'),
config = require('./nuxt.config'),
app = require('express')();
const nuxt = new Nuxt({...config, ...{ dev: !isProd }})
app.use(nuxt.render)
if (!isProd) {
const builder = new Builder(nuxt)
builder.build()
}
app.listen(3000)
I run nuxt build which results in entrypoint files: Entrypoint app = 32847580a74f1882ab1a.js 627079640005b2aff141.js ff5b142fabf2940dccee.js cb8be830c6794eb9ee84.js which… are somewhat meaningless to me, I’m guessing they’re handled internally (?).
I then run:
NODE_ENV=production node server.js, and try to navigate to localhost:3000/
The error occurs:
Renderer is loaded but not all resources are unavailable! Please check /.nuxt/dist/server existence.
I can confirm that a server folder exists. Am I doing anything obviously stupid? Thank you.
What is expected ?
The page should render.
What is actually happening?
An error is thrown.
<div align="right">This bug report is available on Nuxt community (#c9064)</div>About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 8
- Comments: 30 (8 by maintainers)
@pi0 The issue is not because of nuxt, we are not running the build before deploying to GCP. After we ran “npm run build” and do a deploy it is working perfectly fine. thanks for time.
Run your application using
npm run dev@pi0
nuxt.config.js
package.json
custom index.js
I’m having this issue on 2.8.1 deploying to AWS ElasticBeanstalk. Did anyone figure out what the problem was?
[Update]: I discovered that my automated build (on Bitbucket) wasn’t generating anything for
nuxt build. No idea why. I’m going to build locally and deploy that version manually until I figure out what is wrong. Thanks for the hints here.[Update 2]: Turns out I had a module under
devDependenciesinstead ofdependenciessonpm install --productionwas skipping it. Oops. Bitbucket build pipeline wasn’t reporting the error fromnuxt build(helpful!). For anyone else with this issue I suggest running your automated deployment tasks locally to make sure.nuxt/distis actually being generated.