data structure that uses the Last In, First Out (LIFO) principle to temporarily store and manage function invocation (call).
one
When we say that the call stack, operates by the data structure principle of Last In, First Out, it means that the last function that gets pushed into the stack is the first to be pop out, when the function returns.
A stack overflow occurs when there is a recursive function (a function that calls itself) without an exit point. The browser (hosting environment) has a maximum stack call that it can accomodate before throwing a stack error.
This is as simple as when you try to use a variable that is not yet declared you get this type os errors.
I know it’s in the name of the errors, but like it says itself, this occurs when you have something that cannot be parsed in terms of syntax, like when you try to parse an invalid object using JSON.parse.
Try to manipulate an object with some kind of length and give it an invalid length and this kind of errors will show up.
Like the name indicates, this types of errors show up when the types (number, string and so on) you are trying to use or access are incompatible, like accessing a property in an undefined type of variable.
breakpoints it is easier to create a code execution in scenarios like this by taking into account the call stack which is available, for example, in chrome developer tools “sources” tab.
the easiest and maybe the most common way its to simply console.log() the variables you want to check or, by using chrome developer tools,