-
Notifications
You must be signed in to change notification settings - Fork 279
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
Node.js paths on macOS are case sensitive #1682
Comments
Functional duplicate of #1646 |
@connor4312 I'm using the latest nightly version and still have this problem. are you sure it's the same problem? |
Can you confirm what version of nightly you're running? THere was an issue in our pipelines that prevented it getting published for a little while |
I tried v2023.4.2817 |
I tried chrome devtools and it can bind breakpoint. |
ok, I figured out why. It's about the case-insensitive file system (macOS default). I started the program with cc @connor4312 can you open the issue? although I have already fixed the problem by making the file casting consistent. |
I think I just hit this bug (also on MacOS) in a much simpler case without any source maps or transpilation, just a simple Node ran the file (and Here's my config, in case it's helpful: {
"name": "validstrings.mjs",
"request": "launch",
"type": "node",
"runtimeArgs": ["polyfill/test/validstrings.mjs"],
"console": "integratedTerminal",
"internalConsoleOptions": "neverOpen",
"autoAttachChildProcesses": true,
"skipFiles": [
"<node_internals>/**",
"**/node_modules/**"
]
}, Once I fixed the filename to the actual "validStrings.mjs" (capital S) then it worked great. |
Describe the bug
Cannot find source map.
To Reproduce
Steps to reproduce the behavior:
npx hereby watch-min
launch.json
Start VSCode and then attach to the language service.
Log File
vscode-debugadapter-cff4305c.json.gz
I found there is something strange happened in the logfile:
Version: 1.77.3 (Universal)
Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
Date: 2023-04-12T09:19:37.325Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin arm64 22.4.0
Sandboxed: No
JavaScript Debugger (Nightly)
v2023.4.1317
The text was updated successfully, but these errors were encountered: