cssauron is a tool which maps the ideas of querying for DOM elements
through CSS selectors (eg how jQuery operates), and mapping that to
cssauron itself is AST agnostic and there are plugins
for a few options that map the concept of selectors to the relevant
AST nodes. The implementation I used was
binds with the
One of the problems with this setup is as you're learning it's hard to
get visual feedback on what might match your css selectors. If I, for
instance, am searching for
variable > id, that is "the identifier
that is part of a variable declaration" aka the variable name, it's
difficult to know which one of those things match. To fix this, I
built what amounts to a Regular Expression tester for these selectors.
You may ask, if it's not clear how the selectors work, why would you
bother? There are a few neat things that you can do when you can
pin-point nodes in an AST. One option here is to report on whether
they're well formed or not. This is the idea behind
jsl, which is a
modular linter that you can customize. Another option is to transform
these nodes, which is what is what the
rewrite-js project aims
for. These are powerful tools, so increasing the ease of adoption
seems like a worthy goal.
frontend: jquery, lodash, bootstrap, bower
backend: flask-router, cssauron-falafel, falafel, underscore, formidable, circular-json, supervisor, mocha
I also link out to http://json.parser.online.fr/ for showing big json nodes.
Voting is now closed.
Uva Wellassa University of Sri lanka
Kun.io App Studio LLC