PackageTrack Sign in Track my project

css.escape

A robust polyfill for the `CSS.escape` utility method as defined in CSSOM.

1.5.1 208M downloads/mo #1035 most downloaded on npm mathiasbynens/CSS.escape

What this package is like to depend on

Last release 10 years ago

no release in 18 months

Release timing varies

gaps range from 4 weeks to 1.3 years

This project publishes no release notes

the list below is its commits, not an announcement

Nothing withdrawn

no release was ever pulled

13 years old

10 releases · first in 2013

0 releases in the last 12 months

see the full history below

Release timeline

10 releases · Oct 2013 to Aug 2016
2014 2016 2018 2020 2022 2024 2026
Release Pre-release

Releases

latest 10
  1. 1.5.1 23 Aug 2016
    Commits, not release notes

    This project publishes no release notes. Between v1.5.0 and v1.5.1 there were 2 commits, 1 of them substantive:

    • Make CSS.escape() without arguments throw
  2. 1.5.0 21 Jan 2016
    Commits, not release notes

    This project publishes no release notes. Between v1.4.0 and v1.5.0 there were 3 commits, 2 of them substantive:

    • Test U+FFFD itself
    • Fix UMD: anonymous modules require dependencies
  3. 1.4.0 03 Dec 2015
    Commits, not release notes

    This project publishes no release notes. Between v1.3.0 and v1.4.0 there were 2 commits, 1 of them substantive:

    • Serialize U+0000 as U+FFFD, not as \FFFD
  4. 1.3.0 01 Dec 2015
    Commits, not release notes

    This project publishes no release notes. Between v1.2.0 and v1.3.0 there were 3 commits, 2 of them substantive:

    • Expose escape via UMD to work around WebKit bug
    • Lowercase escaped code points as per the spec
  5. 1.2.0 01 Dec 2015
    Commits, not release notes

    This project publishes no release notes. Between v1.1.0 and v1.2.0 there were 2 commits, 1 of them substantive:

    • Serialize U+0000 as \FFFD instead of throwing
  6. 1.1.0 10 Sep 2015
    Commits, not release notes

    This project publishes no release notes. Between v1.0.0 and v1.1.0 there were 3 commits, 2 of them substantive:

    • Update spec links
    • Match spec update
  7. 1.0.0 09 Sep 2015
    Commits, not release notes

    This project publishes no release notes. Between v0.2.1 and v1.0.0 there were 3 commits, 2 of them substantive:

    • Add MIT license file
    • Match spec update
  8. 0.2.1 01 Jun 2014
    Commits, not release notes

    This project publishes no release notes. Between v0.2.0 and v0.2.1 there were 3 commits, 3 of them substantive:

    • Set up Coveralls
    • Ensure the name of any error instances is 'InvalidCharacterError'
    • Tag the v0.2.1 release
  9. 0.2.0 30 Apr 2014

    Nothing published for this version

  10. 0.1.0 15 Oct 2013

    Nothing published for this version

Stop reading changelogs one package at a time.

Point PackageTrack at your project and get told which of your dependencies moved, which of those matter, and what to do about it.

Track my project