Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't copy watchdog.js because it doesn't exist in Nightly version #1522

Closed
yume-chan opened this issue Jan 18, 2023 · 1 comment
Closed
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@yume-chan
Copy link

Describe the bug
When opening a folder, VSCode show a notification like this:

ENOENT: no such file or directory, copyfile 'c:\Users\simon\.vscode-insiders\extensions\ms-vscode.js-debug-nightly-2023.1.1617\src\bootloader.js' -> 'c:\Users\simon\AppData\Roaming\Code - Insiders\User\workspaceStorage\9d4000f75dd35d0e77394ad500a55aef\ms-vscode.js-debug-nightly\bootloader.js'

To Reproduce
Steps to reproduce the behavior:

  1. Install the Nightly version
  2. Open a JavaScript project
  3. See error

Log File

VS Code Version:

Version: 1.75.0-insider (user setup)
Commit: 1379f0375440df946adc62f7afb8375dd45d5adf
Date: 2023-01-17T05:21:07.217Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.25276
Sandboxed: Yes

Additional context

Extension version: v2023.1.1617

As #1515 (comment) said:

The bootloader file is still bootloader.bundle.js in the built VSIX... But this PR changed it to bootloader.js, the extension now fails to find it.

There is only bootloader.bundle.js in 'c:\Users\simon\.vscode-insiders\extensions\ms-vscode.js-debug-nightly-2023.1.1617\src folder.

This issue also happens to the watchdog.bundle.js vs watchdog.js file.

@yume-chan yume-chan added the bug Issue identified by VS Code Team member as probable bug label Jan 18, 2023
@connor4312
Copy link
Member

Duplicates #1520

@connor4312 connor4312 added *duplicate Issue identified as a duplicate of another issue(s) and removed bug Issue identified by VS Code Team member as probable bug labels Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants