Can I get node --inspect to open Chrome automatically

前端 未结 9 1969
孤城傲影
孤城傲影 2020-12-13 03:41

In the new versions of node, node-inspector is built in and can be fired using the command node --inspect index.js. However, this always provides a command line

9条回答
  •  轮回少年
    2020-12-13 04:10

    I was searching an answer for the same problem and I discovered two nice tools:

    • Node inspector Manager
    • Node.js V8 Inspector

    NIM seems more advanced, it's able to auto-detect node instances which plays very nice with my current setup. I use nodemon to automatically restart node server whenever a file is changed. Even further than this I setup Webpack with HMR (Hot module reload) and I have total coverage of /public and /server folders. It took me 2 weeks to learn how to setup but now it's starting to pay off.

    npm install -g nodemon
    npm install -g ts-node // In case you use typescript
    

    nodemon.json

    {
        "verbose": false,
        "watch": ["server/**/*.ts"],
        "ext": "ts js json",
        "ignore": ["server/**/*.spec.ts"],
        "exec": "set DEBUG=app:*,-not_this & ts-node --inspect --debug-brk server/main.ts"
    }
    

    set DEBUG=app:*,-not_this is used to enable output from Visionmedia debug

    (!) Currently there is an issue with debug() not printing text in chrome inspector, However for the moment at least the text is visible in the command line. I use command line to see the debug statements and inspector to expand objects.

    Edit

    Meanwhile I found a rather ugly fix but I does the job, partly... Color metadata is ignored and worse it's rendered in the strings. So it's badly affecting the readability. But hey... I got some logs coming out, better then nothing.

    Another issue I had recently is that NIM was not connecting properly. Eventually I figured out that I need to input the actual IP address 127.0.0.1 in NIM config panel instead of localhost

    debugOff it's just an improvised way to have logs closed temporarily until I need them back again.

    // Debug
    let debugOff = (...any: any[]) => { }, debug = require('debug')('vs:ServerApp');
    
    // Workaround for debug working with node inspector in chrome
    let Debug = require('debug');
    Debug.log = console.log.bind(console);
    
    
    /** 
     * Listen for incoming requests
     */
    public listen(): void {
        debug('Start server');
        debugOff('Server port:', SERVER.port); // This would be usually too verbose
    

提交回复
热议问题