Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VSCode debugging is macOS-specific

See original GitHub issue

In .vscode/launch.json:

“runtimeExecutable”: “${workspaceRoot}/dist/GitHub Desktop-dev-darwin-x64/GitHub Desktop-dev.app/Contents/MacOS/GitHub Desktop-dev”,

I guess we need to make these platform-specific

Issue Analytics

State:
Created 6 years ago
Comments:8 (8 by maintainers)

Top GitHub Comments

1reaction

shiftkeycommented, Jun 6, 2017

It doesn’t seem to be working since we updated to webpack 2, as the config returned has changed significantly:

$ npm run debug

> @ debug /Users/shiftkey/src/desktop/desktop
> cross-env NODE_ENV=development node script/debug

/Users/shiftkey/src/desktop/desktop/script/debug:13
  publicPath: config.output.publicPath,
                           ^

TypeError: Cannot read property 'publicPath' of undefined
    at Object.<anonymous> (/Users/shiftkey/src/desktop/desktop/script/debug:13:28)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.runMain (module.js:605:10)
    at run (bootstrap_node.js:427:7)
    at startup (bootstrap_node.js:151:9)
    at bootstrap_node.js:542:3

Applying this version makes the error go away. I think the switch to parallel-webpack has changed other things that we relied on for this script, as running the Renderer as mentioned here doesn’t launch anything 🤔

0reactions

shiftkeycommented, Jun 30, 2017

@iAmWillShepherd i’m going on holidays now, I think you can get to the bottom of this before I get back: