Skip to content

How to keep backend server alive while error occurs for better DX #5

Closed
@fortezhuo

Description

Hi,
First of all, this is not bug of vike-node, but I think some feature idea to improve for better DX.

On example code server/index.js, I add / for triggering error

import express from 'express'
import vike from 'vike-node/connect'

startServer()
/ // for triggering error

function startServer() {
  const app = express()
  app.use(vike())
  const port = process.env.PORT || 3000
  app.listen(port, () => console.log(`Server running at http://localhost:${port}`))
}

And it cause error and app exited with code 1

ReferenceError: startServer is not defined
    at /Users/forte/Downloads/express-react/server/index.js:4:1
    at instantiateModule (file:///Users/forte/Downloads/express-react/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:52650:5)
ReferenceError: startServer is not defined
    at /Users/forte/Downloads/express-react/server/index.js:4:1
    at instantiateModule (file:///Users/forte/Downloads/express-react/node_modules/vite/dist/node/chunks/dep-mCdpKltl.js:52650:5)
error: script "dev" exited with code 1

I have tried to use pm2 but still not get better DX

Any idea for better DX ?

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions