So one of the things just to kind of point out
is when you are debugging apps, you can just go up here
and you can see there's always warnings and then errors.
So very similar for your console when you're in VS Code.
And all of these are just telling you things like,
oh, this is not supported in web.
So you can still use it, but this particular feature
is not supported in web.
And so we just have it hidden.
And so I mean, none of the warnings
are really relevant to us right now.
But when the errors pop up, they'll
tell you exactly what the error is.
And then if you click on it, it'll
take you down into the component to fix.
And then also, if there's a red error here,
like if there's a 1 or a 2 up there and it's showing an error,
you cannot build the app until it's fixed.
So it doesn't even let you try to build it
until you have all your bugs fixed.
So that's just something to keep in mind.
Off the top of my head, I'm trying to think,
could I delete something and show you
what that error looks like?
But at this point, I don't want to break it.
No, no, you shouldn't break it.
But let's say I deleted a local state of something.
That would then find all the places where that's now
missing, and those will all show up as errors.
And I would have to click on each one and update it.
So in the next little section, what we'll do
is we'll actually delete a variable,
because we actually need to do that.
And then I'll show you what that error log looks like.
OK, cool.