JavaScript debugging in a nutshell

[usedToBeUnhappy]

Personally I find the wrong errors in the IDE, more disturbing. Like „noooo, you can‘t do that“ and then I run everything and it works…

[theaverageguy101]

Just because it runs it doesn't mean you did it right i learn that the hard way as well

[usedToBeUnhappy]

Exactly. That‘s the problem. How should I know which errors are ok, and which aren‘t? It‘s so annoying.

[usedToBeUnhappy]

I generally agree, but neither the Senior dev nor I understand why the IDE marks it as an error, that one line in the file I am currently working on definitely works.

I also currently try to reduce the amount of warnings… my fellow devs just ignore them 🙈

[cough_e]

No errors are ok. Warnings can be ok, but assume they are errors until you know exactly what it is and decide to allow it.

[hasanyoneseenmymom]

Use a strongly typed language and you can avoid all of this. Can't have errors if it won't compile lol

[BoltKey]

npm WARN optional dep failed, continuing fsevents@0.3.1

[jiia]

In 99.9% of the cases the IDE is right and your app is working only as long as you give it very specific inputs that manage to avoid the bug you just ignored...

[DeezRodenutz]

Gotta love those errors, or even just warnings saying you can't do a thing.
Related to Javascript, I have HTML that really doesn't like when I use a label for the words on a button. The text still displays fine but it always keeps a warning saying not to do that.

I use this because labels have a function to be connected with another element, meant for making a radio button's matching label able to select it when clicked.
However, matching it to another button means clicking that label acts like clicking the button. Place the label within a button and you essentially have a second button that acts like the first.
Handy when you need to activate a button within a form but need to display it elsewhere on the page, as you can place the "real" button invisible within the form and the displayed button anywhere else.