escape-string-regexp breaking changes
npm8 curated breaking changes across major versions of escape-string-regexp. Use this as a migration checklist before bumping dependencies.
- v4.0.0 \u2192 v5.0.0breaking
Require Node.js 12 aebb6e8
- v4.0.0 \u2192 v5.0.0breaking
This package is now pure ESM. Please [read this](https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c). https://github.com/sindresorhus/escape-string-regexp/compare/v4.0.0...v5.0.0
- v3.0.0 \u2192 v4.0.0breaking
Escape `-` in a way that’s compatible with PCRE (#23) ec45c70 Shouldn't be breaking to most users, but if you depend on the exact output, it slightly changed. https://github.com/sindresorhus/escape-string-regexp/compare/v3.0.0...v4.0.0
- v2.0.0 \u2192 v3.0.0breaking
Require Node.js 10 70deac5
- v2.0.0 \u2192 v3.0.0breaking
Escape `-` in a way that’s compatible with Unicode patterns (#21) 732905d https://github.com/sindresorhus/escape-string-regexp/compare/v2.0.0...v3.0.0
- unknown \u2192 v2.0.0breaking
Require Node.js 8 (#13) ea98098 Enhancements:
- unknown \u2192 v2.0.0breaking
Also escape `-` e76291d
- unknown \u2192 v2.0.0breaking
Add TypeScript definition (#13) ea98098 https://github.com/sindresorhus/escape-string-regexp/compare/v1.0.5...v2.0.0
Get this data programmatically \u2014 free, no authentication.
curl https://depscope.dev/api/breaking/npm/escape-string-regexp