Nuxt.js: Need better way to logs error on Server Error page?

[chanlito]

All I get is the below image, nothing else.

How can I know what went wrong?

The following is my setup.

const cors = require('cors')({ origin: true })
const express = require('express')
const functions = require('firebase-functions')
const fs = require('fs')
const path = require('path')
const { Nuxt } = require('nuxt')

const nuxtDir = path.resolve('.', 'nuxt')
if (fs.existsSync(nuxtDir)) {
  console.log('Nuxt directory exists.', nuxtDir)
} else {
  console.error('Nuxt directory does not exists.', nuxtDir)
}

const app = express()
const nuxt = new Nuxt({ dev: false, buildDir: 'nuxt' })

app.use(cors)
app.use(nuxt.render)

exports.render = functions.https.onRequest(app)

It works if i run firebase serve --only functions,hosting locally
But doesn't when i deploy it to firebase and show the above image.

_{This question is available on Nuxt.js community (#c1816)}

[atmar]

Same question here but with different server code. How do I log the errors?
Doing this I can see the errors on the page, but I don't want to do that in production.

module.exports = {
  debug: true
}

const { Nuxt, Builder } = require('nuxt')

const https = require('https')
const fs = require('fs')
const isProd = (process.env.NODE_ENV === 'production')
const port = process.env.PORT || 3000

// We instantiate nuxt.js with the options
const config = require('./nuxt.config.js')
config.dev = !isProd
const nuxt = new Nuxt(config)

// Render every route with Nuxt.js

// Build only in dev mode with hot-reloading
if (config.dev) {
  new Builder(nuxt).build()
  .then(listen)
  .catch((error) => {
    console.error(error)
    process.exit(1)
  })
}
else {
  listen()
}

function listen() {
    const options = {
key: fs.readFileSync('/home/certs/localhost.key'),
cert: fs.readFileSync('/home/certs/localhost.crt')
};
  // Listen the server
// Create the server
https
.createServer(options, nuxt.render)
.listen(port)
  console.log('Server listening on `localhost:' + port + '`.')
}

[danieloprado]

Where is the logs?

[aweapp]

I also addressed the same problem.
adding the following code to nuxt.config.js, we were able to display error details in production( or staging project) as well.
@atmar thanks for the example!
( not native english :) )

process.env.DEBUG = 'nuxt:*'

module.exports = {
  debug: true,
...

In my case, I am getting better by adding a module.

yarn add regenerator-runtime
yarn add core-js
...
firebase deploy

[chanlito]

@yoidotco do you have a repo that I can take look at?

[aweapp]

@BruceHem
It is not yet.
If you have nuxt.config.js in your repository, please add debug: true, to it :)

[chanlito]

Ok, I can confirm that putting debug: true shows the error.

I had to install all nuxt dependencies manually, somehow specifying just nuxt in package.json is not enough.

[danieloprado]

Please don't close this issue, debug: true is not a good solution because shows the error at the browser, we need an way to see the log without exposing the code!

[pi0]

https://trello.com/c/rojBtVqz

[aweapp]

This may be able to be use. for firebase functions(SSR).
express-winston + Stackdriver Trace
https://cloud.google.com/nodejs/getting-started/logging-application-events
https://github.com/GoogleCloudPlatform/nodejs-getting-started/blob/master/5-logging/app.js

I'm going to try it out.
If it works, I will publish the source :)

[besnikh]

@yoidotco is there any update on this ?

[CKGrafico]

Working well here!

[chanlito]

Hey guys, since the latest Nuxt version uses async/await by default (node 8), firebase cloud function will not work since it's still using only node 6. Any workarounds?

[davidroyer]

@chanlito

I was wondering the same thing. Any luck?

[chanlito]

@davidroyer nope

[husayt]

@danieloprado what is the latest on this? Can we close it?

[atmar]

Please don't close it. There is still a need to send the logs to a file instead of having to use
module.exports = {
debug: true
}
to show them on the website itself.

[bovas85]

@pi0 @husayt any idea on how to solve this? The trello is archived but I can't see a solution

[atmar]

@pi0 I'm pinging this thread again. This is a really important feature. Even today I had unexplained errors for users and there is no way for me to check. It says "check the logs" but there are no logs and I can't expose debug to true in production, that's a horrible solution

[aldarund]

@atmar you could use nuxt/sentry module. Or look at it's code and write same module to send errors to file or to whatever you want to

[galvez]

As @aldarund mentioned, nuxt/sentry should provide all pointers needed for implementing similar functionality.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.