why you don't need console.log

[@bishal_mishra99]

Cool. How do you log dynamic values

[@harshitgupta275]

Did you find any answer?

[@ulfgj]

this we need.

[@DJReRun]

Also, where is the "log point" stored? Is it in an external file that's _near_ to the source so that it can be tracked by source control or is it only local to VSCode and the current user?

[@christopherfox6914]

If you mean variables, use {variablename} in your log point message.

[@vulkanosaure]

It's a great advice for people who aren't using a debugger

[@dantek3050]

".. there are two types of people" applies heavily in this matter

[@elProdigio]

Nice feature. Before this feature exists I remember to use conditional breakpoints to put console.log inside of the condition (it never stops because console.log return a falsy value). I also use conditional breakpoints to change some data conditionally. For example change user variable to "test" when the amount value is 999. This code will be into the condition of the breakpoint: amount === 999 && user="test" && false About the video the only "but" is that you need to run the code into a debug session (slower), and depending on how the protect is configured, is not always possible to debug.

[@muraliavarma]

This feature also exists in the chrome dev tools btw. Very useful for quick debugging on the browser

[@dytra_io]

does this feature supports expression/variable ? because I often console log the request/response

[@mahmood466]

Does it support string interpolation, something like "here value is ${value}"?

[@SwoggersLOL]

Yea, but you could merge the print statements into a write stream function so that you could make a log file at the same time you're printing logs

[@VishalPawarR]

Looks clean but removing the logpoint console after adding is an extra step!

[@nicolasmayorga8288]

That's amazing but what if I need to log a variable?

[@ayviuon]

Multiple steps just to put a logpoint seems like alot of hassle, writing console log is quicker 🤷‍♂️

[@joergw]

Thanks, never heard about log points before

[@good-dev-student]

Cool any other tricks like this ❤

[@AkukweEbube]

Didn't know about this. Nice one

[@anu1o]

Awesome 👍🏻 🔥

[@asanka.abewickrama]

Wow, that's very helpful for me.🎉

[@tubero911]

Works in other languages too: python, dart, lua, and java.

[@mick_io]

Still waiting on VS Code to offer a full feature mouse free workflow. Till then, nope.

[@caujka]

Blimey, this is so awesome!

[@deheinrich4785]

This hint came just in time thanks! Will these Statements appear in the terminal that I do npm run dev with?

[@jakubtomas21]

What if want to see data in property? Like response data

[@second9320]

All pushes with log or todo give warning these days. What is this for?

[@DanielEnesi17]

Wow. That's awesome - and convenient. Thanks!

[@ayivugwekabemba]

Wow. Thank you. I didn't know this one.

[@investkalimot7499]

how to logs the variables?

[@shivjirwankar1993]

Awesome. Much needed feature.

[@ste-fa-no]

Would those be exportable/importable?

[@martygo]

Awesome 🎉

[@mohamedkarim-p7j]

Thank for sharing

[@alihelmi]

How to log variables?

[@VictorMartins239]

can it log variables? it doesnt look it does

[@rajgopaljakhmola6080]

But what about logging into the browser?

[@Twas-RightHere]

Doesn't work for client code though, which is what most react apps are...

[@debjyotibanerjee6382]

Will the log points be visible in browser console?

[@mukundm2023]

Does it work for all major languages or just js?

[@rotimibest8530]

How do I remove log points?

[@henryantwi8222]

This is very useful 👌 👍

[@wzup23]

Wow! Thus one's great feature.

[@arturomedina2055]

Does this work with tools like Vite?

[@prana-ayama]

Will the registered logpoints be shared with git?

[@kingmaxilla]

👍🙂👍

[@ruralanemone6633]

convenient, yeah portable, no hello monopoly?????

[@prajwalitsinghraja3196]

I will give it a try, it's worth it, I think so.

[@Redragon2501]

Can't make it work in my vue.js app

[@pang12345]

Is that only possible in debug mode?

[@TheAbhishekJadhav]

Ftw why haven’t I seen this earlier 😮

[@rahulpurohit6246]

Does it work for react native

[@NilisW]

Good one

[@rakysreplays8259]

Very useful, thanks

[@sssrikanthhh]

Nice trick 👍

[@armangohari6193]

Nice one.

[@4w0ken]

or just, and maybe im tripping, use the debugger

[@beyondcrud]

Wow very helpful

[@TheBambooooooooo]

Beautiful

[@samnmeje3486]

this is awesome

[@hanibachi5228]

Now thats a usefull short

[@applernb3773]

The point is Not much visible though

[@rockmonty]

👍

[@marlo3464]

this does not gonna work in production. It is ok for frontend, but for backend you critically need to have logging in your system

[@samuelvalentine7846]

This is niceee

[@biggaji0]

great feature

[@sergiobenitez1468]

this is gold

[@stonecoder8697]

This is big for I.

[@yassine-sa]

That's neat

[@JermaineMorgan]

Get outta here!!!!

[@OggVorbis69]

Now does the log statements appear in the source?

[@khatmanworld]

Not sold. Thanks. Console.log for life

[@yassinebenkraouda]

Console.log is good why drop it?

[@stefancomandant8683]

Nope, mine say console.log("shit1") console.log("shit2") console.log("shit3")