Know when breakpoints are entered/exited due to a window resize.
If you are sane and use npm:
npm install break
If you are not sane, grab the bundled standalone version at standalone/break.min.js.
Including this on your page will assign
var createBreakpointManager =var bm =bmbmbm
Create a breakpoint manager.
bm inherits from the node event emitter so it has the same API in addition to the methods below.
The following events are emitted by this module:
enter:[breakpoint]- when a breakpoint is entered, e.g
exit:[breakpoint]- when a breakpoint is exited, e.g
Add a breakpoint with a name and a media query. On every window resize event, the media
query will be tested. If the result changes to
mq being satisfied, the event
will be emitted. If the result changes such that
mq is no longer satisfied, the event
exit:[name] will be emitted. If no change occurs, no events are emitted (as this would
be chaos on every window resize event!).
The media query is also tested once when it is added, as it is often helpful to know whether
mq is satsfied at this point. This check happens on
process.nextTick() so that
it does not matter whether you add the listeners (with
.on()) before or after you add the
This function delegates the first two arguments to the event emitter
.on(). The third argument is a flag as to whether this function
should run once if media queries are not supported.
Runs the function
fn if media queries are not supported.
This is quite a simple module, however it's annoyingly tricky to test. However,
this has been acheived by having two browser test suites –
The caveat is that these tests have to run in a browser by hand.
All bug fixes and features require that (if possible) test is added which fails before the implementation of the new code, and passes afterwards.
git clone firstname.lastname@example.org:bengourley/break.gitcd breaknpm install
Then use the links presented in the terminal to run the tests in various browsers. You will be prompted to resize your browser at points during the test.
The modern tests should pass in IE9+, Firefox, Safari and Chrome. The legacy tests should pass in IE6,7,8.
Note: you may need to replace a portion of the links if using a VM. I am using
VirtualBox, so the route to my development
the url I use to run the legacy tests on IE6 inside my VM is:
npm run standalone
This needs to happen before every release.
BSD. Bundled in with this module is an IE9 matchMedia polyfill by Scott Jehl et al. with a BSD/MIT license.
Ben Gourley, Nick Price.