You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally speaking, a few versions ago, Netlify CLI worked without any problem, but I think it was more than one year ago last time I debugged a function.
I read the manual (RTFM), I read a few old issues, I read a few posts in the forum, I tried different setups, but the result didn't change: the breakpoint is not triggered.
Weird workaround
Set the breakpoint to the generated or bundled function .netlify/functions-serve/hello/netlify/hello.mjs
instead of netlify/functions/hello.js
With the workaround eventually the debugger stops to the breakpoint.
Describe the bug
Windows 11 / Powershell
7.4.6
/ VSCode1.95.3
/ Netlify CLI17.38.0
The breakpoint is not triggered.
Generally speaking, a few versions ago, Netlify CLI worked without any problem, but I think it was more than one year ago last time I debugged a function.
I read the manual (RTFM), I read a few old issues, I read a few posts in the forum, I tried different setups, but the result didn't change: the breakpoint is not triggered.
Weird workaround
Set the breakpoint to the generated or bundled function
.netlify/functions-serve/hello/netlify/hello.mjs
instead of
netlify/functions/hello.js
With the workaround eventually the debugger stops to the breakpoint.
Any hint?
Steps to reproduce
JavaScript Debug Terminal
ntl dev
(Netlify CLI installed globally)Debugger attached.
displayednetlify/functions/hello.js
http://localhost:8888/.netlify/functions/hello
Configuration
netlify.toml
: nonehello.js
Environment
The text was updated successfully, but these errors were encountered: