question-mark
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-nix script cannot find the other executables

See original GitHub issue

Preflight Checklist

Issue Details

  • Electron Forge Version:
    • 6.0.0-beta.47
  • Electron Version:
    • v7.1.7
  • Operating System:
    • macOS 10.15.2

Expected Behavior

Using the launch configuration from https://www.electronforge.io/advanced/debugging in VS Code enables debugging for the new application.

Actual Behavior

The launch configuration errors with:

/Users/liamdawson/w/orcharduml/node_modules/.bin/electron-forge-vscode-nix --inspect-brk=35706 
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '/Users/liamdawson/w/@electron-forge/cli/dist/electron-forge-start'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
    at startup (internal/bootstrap/node.js:283:19)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

To Reproduce

  • yarn v1.21.1
  • npm v6.13.4
  • node v10.16.3

Additional Information

I’m guessing it’s related to something about package nesting and/or symlinks?

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:4
  • Comments:9

github_iconTop GitHub Comments

24reactions
kreslicommented, Mar 20, 2020

to fix it the electron-forge-vscode-nix file must be change from

#!/usr/bin/env bash
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

ARGS=$@
ARGS=${ARGS// /\~ \~}

node $DIR/../../../@electron-forge/cli/dist/electron-forge-start --vscode -- \~$ARGS\~

to

#!/usr/bin/env bash
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"

ARGS=$@
ARGS=${ARGS// /\~ \~}

node $DIR/../@electron-forge/cli/dist/electron-forge-start --vscode -- \~$ARGS\~
6reactions
sloan-dogcommented, Sep 17, 2021

This is still an issue as of electron-forge @ 6.0.0-beta.61

Currently, patching this manually. Kinda brutal. Lets fix?

Read more comments on GitHub >

github_iconTop Results From Across the Web

vscode-nix script cannot find the other executables · Issue #1369
I have searched the issue tracker for a bug that matches the one I want to file, without success. I did find Cannot...
Read more >
Developers - vscode-nix script cannot find the other executables -
Coming soon: A brand new website interface for an even better experience!
Read more >
Command line options to executable in a VSCode extension
I tried to give command line arguments to the executable using the ... With this one, I get an unknown option error from...
Read more >
Running Visual Studio Code on Linux
Get Visual Studio Code up and running on Linux. ... Note that other binaries are also available on the VS Code download page....
Read more >
How to Fix Cannot Find Script File in Windows 10 [Tutorial]
How to Fix Cannot Find Script File in Windows 10 [Tutorial]Registry Value: C:\Windows\system32\userinit. exe,A Windows Script Host error can ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found