Nuxt `npm run dev` crashed with odd characters
I created an application with koa/nuxt/knex around 1 year ago... about 3 days ago it stopped working and as a temporary solution I decided to simply restart the application in dev mode to log a couple of things but I am not able to start it on my server anymore and I get some odd characters.
Locally I was able to start the application without a sweat (or almost: since my server is in maintenance mode I discovered that I was not doing a couple null checks which were missing, but no big deal).
Does anyone know how to fix this, how I could provide more data or has any suggestions to give about how to inspect this?
A series of things happened:
- Another process in the server started to request more and more RAM
- A peak of connections happened
This lead the nodemon to a crash.
Trying to restart the nodemon via dev environment (npm run dev) also triggered a local build, which (with no surprise) requests RAM... since the other process was still active, this resulted in the build process misbehaving.
Solutions were:
- Build locally, ship the built version which in my case simply meant to just use
npm run startagain. (which was still not enough for me in order to understand what caused the issue in the first place) - Stop the memory-consuming process
- Get more RAM
- Invalid options object. Dev Server has been initialized using an options object that does not match the API schema
- What is the (smallest) setup to allow import to be used by Jest?
- How can the default node version be set using NVM?
- Uncaught ReferenceError: Buffer is not defined
- How to properly delete data from a table and chain the deletion
- How do I test a Node.JS Script that is not a module and runs as soon as it's called?
- Testing JavaScript Written for the Browser in Node JS
- 'You are running version ' + process.version + ' of Node.js, which is not supported by Angular CLI v6
- Update BigQuery table with an array of objects where some of the values may be null
- Using multer diskStorage with Typescript
- Error: Could not resolve various Storybook dependencies with Storybook 8 and PNPM
- Do global augmentations need to be imported as a side effect in the consumer?
- npm ERR! Refusing to delete / code EEXIST
- How to allow ':' character in Node.js Express routes (Google custom methods)
- nodemon + express, listen port =?
- NextAuth: how to return custom errors without redirection
- npm publish fails with GitLab NPM registry
- How to end server in VSCode after closing terminal window
- AWS SDK file upload to S3 via Node/Express using stream PassThrough - file is always corrupt
- Github API is responding with a 403 when using Request's request function
- Refactor AWS cdk stack into multiple smaller stacks
- "React.Children.only expected to receive a single React element child" error when putting <Image> and <TouchableHighlight> in a <View>
- Firestore set doc with merge option true or update doc
- node:console test is producing TypeError: Console is not a constructor
- setState doesn't update the state immediately
- Unknown file extension ".ts" for a TypeScript file
- Axios delete method
- Re-throwing exception in NodeJS and not losing stack trace
- Firebase Functions "cannot determine backend specification"
- Cant access Firebase Admin SDK via Node.js on my VPS, but I can on my local machine