Mirrors/sizzle
1
0
Fork 0
mirror of https://github.com/jquery/sizzle.git synced 2025-12-28 04:43:44 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
A sizzlin' hot selector engine.
1,041 Commits 4 Branches 59 Tags 5.7 MiB
JavaScript 55.7%
HTML 39.4%
CSS 4.9%
4194dc464e
Go to file
Michał Gołębiowski-Owczarek 4194dc464e
Docs: Update the command to clone the repo
2023-02-14 19:24:56 +01:00
.github/workflows Tests: Migrate from Travis to GitHub Actions 2022-01-10 18:08:58 +01:00
build Release: Make Sizzle work with jquery-release, remove generated files 2020-03-02 20:29:32 +01:00
dist Release: Make Sizzle work with jquery-release, remove generated files 2020-03-02 20:29:32 +01:00
external Tests: Fix speed/index.html dependencies 2018-10-25 17:46:15 +02:00
speed Build: Switch from JSHint & JSCS to ESLint 2019-05-29 17:01:29 +02:00
src Selector: Stop relying on CSS.supports( "selector(...)" ) 2023-02-14 13:13:00 +01:00
tasks Release: Make Sizzle work with jquery-release, remove generated files 2020-03-02 20:29:32 +01:00
test Build: Update tested browsers 2023-02-14 13:36:51 +01:00
.bowerrc Use bower for speed framework dependencies. Add .bowerrc. 2013-08-27 14:59:05 -04:00
.editorconfig Build: Switch from JSHint & JSCS to ESLint 2019-05-29 17:01:29 +02:00
.eslintignore Build: Switch from JSHint & JSCS to ESLint 2019-05-29 17:01:29 +02:00
.eslintrc-browser.json Build: Switch from JSHint & JSCS to ESLint 2019-05-29 17:01:29 +02:00
.eslintrc-node.json Build: Run Karma tests sequentially in separate processes + other improvements 2019-08-21 16:57:14 +02:00
.eslintrc.json Build: Switch from JSHint & JSCS to ESLint 2019-05-29 17:01:29 +02:00
.gitattributes Build: Normalize line endings 2014-04-14 11:32:53 -04:00
.gitignore Release: Make Sizzle work with jquery-release, remove generated files 2020-03-02 20:29:32 +01:00
.mailmap Build: Update my name in .mailmap & AUTHORS.txt 2017-08-28 23:19:13 +02:00
.npmrc Build: Add .npmrc with save-exact=true 2016-05-24 14:49:13 +02:00
AUTHORS.txt Release: Update AUTHORS.txt 2020-02-28 18:53:00 +01:00
bower.json Build: Remove the version field from the bower.json file 2020-03-30 18:09:59 +02:00
CONTRIBUTING.md Misc: Update jQuery Foundation to JS Foundation 2016-12-02 01:20:31 -05:00
Gruntfile.js Build: Update tested browsers 2023-02-14 13:36:51 +01:00
LICENSE.txt Misc: Update jQuery Foundation to JS Foundation 2016-12-02 01:20:31 -05:00
package-lock.json Build: Update another version in package-lock.json 2023-02-14 19:24:04 +01:00
package.json Build: Updating the main version to 2.3.11-pre. 2023-02-14 19:00:55 +01:00
README.md Docs: Update the command to clone the repo 2023-02-14 19:24:56 +01:00

README.md

Sizzle

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:

  1. Getting Involved
  2. JavaScript Style Guide
  3. Writing Code for jQuery Organization Projects

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 git@github.com: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 install grunt-cli package – npm install -g grunt-cli
  • Open test/index.html in the browser. Or run npm test/grunt test on the command line, if environment variables BROWSER_STACK_USERNAME and BROWSER_STACK_ACCESS_KEY are 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/unit directory.

Developing with grunt

  • npm run build or grunt will lint, build, test, and compare the sizes of the built files.
  • npm start or grunt start can be run to re-lint, re-build, and re-test files as you change them.
  • grunt -help will show other available commands.