This is post presents assertWhichStop.js.
is a simple library which provide an
assert() which stops…
who would have guessed :)
You may find that surprising but in your browser,
does not stop the execution of the code but it does in other languages.
will make your assert stop even in your browser.
assertWhichStop.js is a part of debug.js library, which we talked about in previous posts. This post will explain why it is usefull to stop and how to use assertWhichStop.js. This library is very small , barely 10 lines full total at the time of writing. It is based on a little gist we did in collaboration with jens arp. Ok now let’s see more deeply what is assert.
What Is Assert() ?
Assert is a very usefull tool during developement. It is done to explicitly check internal consistency. In other words, it is a way to say “ok here, this MUST be true. And if it isn’t, there is a bug”. You explicitly describe the assertions you make in your code and get immediatly notified when one happened to be wrong. So you can fix the bug.
Assert is from c / c++. It is available in many languages: in python, php, or even done in perl. In most language, the execution is stopped immediatly: thru exception for python or php , or thru unix signal + coredump with c / c++. Thus you get notified of the bugs early, study the situation and start fixing.
Let’s Get Started
You first need to get the files which contains the code.
As for the rest of debug.js, the global detection works in browsers and in node.js.
If you are in node.js, you do the usual
If you are in a browser, just add a
How To Use It ?
Now that we got the code included, let’s see how to use it. The typical usage will be like that
If the asserted condition is true, nothing will happen.
If it is false, the message will be displayed and it will try to stop the execution of the programm.
Suppose you got a variable
foo which is supposed to always be a number greater than 0.
You will typically do something like that.
This will stop the execution if
foo isn’t greater than 0. Simple enougth :)
Sure but how does it try to stop ? Let’s look at that.
How To Stop ?
assertWhichStop can stop in 2 ways: The first one is by throwing an exception with Error It is the most natural way. So it is the default behavior.
Additionnaly it is possible to stop by triggering the js debugger itself.
This generate a total halt. Nothing will happen anymore in the page.
Unfortunatly it seems to be implemented only on chrome at the moment.
When the virtual machine hits it, it will popup the
so you can get the call stack, get the local variables,
set up conditions to watch or many other things. Usefull stuff to debug.
Overloading Console API for Backward Compatibility
If you wish, you can overload the
console.assert with the following line.
Thanks to that, you can easily take advantage of
assertWhichStop.js without changing your code, a nice feature :)
After this, any
console.assert() will use assertWhichStop and will be able to stop as
soon as an assertion is found wrong.
If this post, we talked about
why assert is usefull during developement to keep your code running as you expect.
We have seen
how to use assertWhichStop.js
to immediatly stop when one of your assertion happened to be wrong.
Thus then you can fix the bug as soon as possible.
We got various ways to stop: exception or
All that in a backward compatible fashion… rather cool if you ask me :)
That’s all folks, have fun!