Nodejs worker not working when running nodejs server from js debug terminal

[ronak1009]

Type: Bug

create a small nodejs express server
run the server using js debug terminal
on sending the request to start worker, the worker code does not start

I asked question on stackoverflow:
https://stackoverflow.com/questions/79317327/nodejs-worker-is-not-getting-called?noredirect=1#comment139868387_79317327

VS Code version: Code 1.96.2 (fabdb6a, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-12850HX (24 x 2419)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.69GB (35.89GB free)
Process Argv	--crash-reporter-id c2d1ca8b-1353-4c5e-9ba7-6e3e9d2df5c5
Screen Reader	no
VM	0%

Extensions (30)

Extension	Author (truncated)	Version
es7-react-js-snippets	dsz	4.4.3
gitlens	eam	16.1.1
vscode-html-css	ecm	2.0.11
copilot	Git	1.254.0
copilot-chat	Git	0.23.2
npm-package-version-bumper	jef	1.6.0
vsc-python-indent	Kev	1.19.0
black-formatter	ms-	2024.4.0
debugpy	ms-	2024.14.0
python	ms-	2024.22.1
vscode-pylance	ms-	2024.12.1
jupyter	ms-	2024.11.0
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.0.21
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
cmake-tools	ms-	1.19.52
cpptools	ms-	1.22.11
cpptools-extension-pack	ms-	1.3.0
sublime-keybindings	ms-	4.1.10
autodocstring	njp	0.6.1
vscode-versionlens	pfl	1.16.1
nodejs-snippets	piy	0.0.2
vscode-thunder-client	ran	2.33.2
velocity	sod	0.3.0
indent-colorizer	tal	1.0.0
cmake	twx	0.0.17
volar	Vue	2.2.0
vscode-todo-highlight	way	1.0.5
JavaScriptSnippets	xab	1.8.0

(2 theme extensions excluded)

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31179979
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

[connor4312]

/jsDebugLogs

[vs-code-engineering]

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to [email protected]