nytimes/kyt

Source mapping of server code is not working when debugging in Chrome Dev tools

Open

#319 opened on Nov 3, 2016

View on GitHub
 (3 comments) (0 reactions) (0 assignees)JavaScript (1,918 stars) (129 forks)batch import
bughelp wanted

Description

Hello and thanks for this tool, it's a huge time-saver.

I use kyt 0.3.0, node 6.7.0 on MacOS Sierra and I want to debug my server code.

I use the dev command with the inspect flag.

kyt dev -- --inspect

and then i open the Chrome Dev Tools using the url printed in the terminal:

Debugger listening on port 9229.
Warning: This is an experimental feature and could change at any time.
To start debugging, open the following URL in Chrome:
    chrome-devtools://devtools/remote/serve_file/@60cd6e859b9f557d2312f5bf532f6aec5f284980/inspector.html?experiments=true&v8only=true&ws=localhost:9229/node

And it works perfectly except the source mapping for my server code. Only, the node_modules are mapped: capture d ecran 2016-11-02 a 15 06 21

Any ideas ?

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingbackend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Node.js debuggingsource mapskyt build setup
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate kyt's server build configuration to see if source maps are generated for server code. Compare with client build setup. Check if the 'dev' command with ' inspect' flag enables source maps. Look at kyt's webpack config or babel settings. The issue may be resolved by updating source map generation or configuring Chrome DevTools to map to local files.