Can not run fastify cli in watch mode with node inspector
See original GitHub issue🐛 Bug Report
Cli is not working in --watch mode with node inspect on the board
It throws the following log: Starting inspector on 127.0.0.1:9230 failed: address already in use
To Reproduce
Steps to reproduce the behavior:
Paste your code here:
node --inspect-brk=9230 ./node_modules/.bin/fastify start --watch -l info -P app.js
Expected behavior
It should work in --watch mode with node inspect on the board
Your Environment
- node version: 10
- fastify version: >=2.0.0
- os: Mac
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:13 (7 by maintainers)
Top Results From Across the Web
fastify-cli - npm
Start using fastify-cli in your project by running `npm i fastify-cli`. There are ... Start fastify app in debug mode with nodejs inspector...
Read more >Getting-Started - Fastify
Getting Started. Hello! Thank you for checking out Fastify! This document aims to be a gentle introduction to the framework and its features....
Read more >Scripts - CLI | NestJS - A progressive Node.js framework
A Nest application is a standard TypeScript application that needs to be compiled to JavaScript before it can be executed. There are various...
Read more >ts-node-dev not restarting when changes made - Stack Overflow
The issue is resolved now. I found out the problem using --debug that it was an error related to 'SIGTERM'. So I added...
Read more >Fastify-Cli | Run a Fastify Application with One Command
Start Fastify app in debug mode with nodejs inspector, -d, --debug, FASTIFY_DEBUG ... By default fastify-cli runs dotenv , so it will load...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, sure Thank you all for your help!
I think this issue can be closed, don’t you @pyxarez ? The initial behaviour can be solved now by using:
fastify start --watch -l info -P app.js -d --debug-port=9230