Chrome has its own Console Utilities API Reference where $ and $$ are offered regardless, among other utils, unless the global scope has been overwritten with something else (i.e. jQuery).
The API for $ and $$ is more jQuery-ish, and if you'd like to reproduce it its like:
To avoid needing polyfills for forEach or Symbol.iterator on NodeList collections, you can also go ahead and convert the static collection as Array so that all methods, including filter and map can be used.
Sorry for replying an old post, but how does this method of aliasing these two query selectors compares to the OP's post for development, especially for the parent parameter?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Chrome has its own Console Utilities API Reference where
$and$$are offered regardless, among other utils, unless the global scope has been overwritten with something else (i.e. jQuery).The API for
$and$$is more jQuery-ish, and if you'd like to reproduce it its like:To avoid needing polyfills for
forEachorSymbol.iteratoronNodeListcollections, you can also go ahead and convert the static collection asArrayso that all methods, includingfilterandmapcan be used.If you don't have
Array.fromin your debug session, or you are after a thin layer that works across browsers, you can go for the following:Sorry for replying an old post, but how does this method of aliasing these two query selectors compares to the OP's post for development, especially for the parent parameter?