jquery/sizzle
jquery/sizzle has 6,296 GitHub stars and 926 forks. GitHot measured -1 stars in 24 hours. Last checked 2026-11-07 12:18 UTC. Last push 2026-01-14.
A sizzlin' hot selector engine.
Measured star growth
- in 24h
- -1
- in 7 days
- Collecting history
- in 15 days
- Collecting history
- in 1 month
- Collecting history
Net star changes over overlapping periods, not daily totals. Missing measurements are left blank. Stars measure attention, not software quality.
README.md
OriginalSizzle
A pure-JavaScript CSS selector engine designed to be easily dropped in to a host library.
Contribution Guides
In the spirit of open source software development, jQuery always encourages community code contribution. To help you get started and before you jump into writing code, be sure to read these important contribution guidelines thoroughly:
What you need to build Sizzle
In order to build Sizzle, you should have Node.js/npm latest and git 1.7 or later (earlier versions might work OK, but are not tested).
For Windows you have to download and install git and Node.js.
Mac OS users should install Homebrew. Once Homebrew is installed, run brew install git to install git,
and brew install node to install Node.js.
Linux/BSD users should use their appropriate package managers to install git and Node.js, or build from source if you swing that way. Easy-peasy.
How to build Sizzle
Clone a copy of the main Sizzle git repo by running:
git clone [email protected]:jquery/sizzle.git
In the sizzle/dist folder you will find build version of sizzle along with the minified copy and associated map file.
Testing
- Run
npm install, it's also preferable (but not necessarily) to globally installgrunt-clipackage –npm install -g grunt-cli - Open
test/index.htmlin the browser. Or runnpm test/grunt teston the command line, if environment variablesBROWSER_STACK_USERNAMEandBROWSER_STACK_ACCESS_KEYare set up, it will attempt to use Browserstack service (you will need to install java on your machine so browserstack could connect to your local server), otherwise PhantomJS will be used. - The actual unit tests are in the
test/unitdirectory.
Developing with grunt
npm run buildorgruntwill lint, build, test, and compare the sizes of the built files.npm startorgrunt startcan be run to re-lint, re-build, and re-test files as you change them.grunt -helpwill show other available commands.
Explore related projects
codecrafters-io/build-your-own-x
Master programming by recreating your favorite technologies from scratch.
560,710 starspublic-apis/public-apis
A collective list of free APIs
496,950 starsmorluto/rea
Reverse engineer anything with agents, from app behavior down to native binaries.
440,310 starsopenclaw/openclaw
The AI that really does things. Any OS. Any Platform. The lobster way. 🦞
394,123 stars