Gathering detailed insights and metrics for perf-regexes
Gathering detailed insights and metrics for perf-regexes
Gathering detailed insights and metrics for perf-regexes
Gathering detailed insights and metrics for perf-regexes
ua-regexes-lite
A lite useragent regexes collection.
eslint-plugin-react-perf
Performance-minded React linting rules for ESLint
regex
Regex template tag with extended syntax, context-aware interpolation, and always-on best practices
perf-marks
The simplest and lightweight solution for User Timing API in Javascript.
npm install perf-regexes
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
12 Commits
3 Watching
1 Branches
1 Contributors
Updated on 24 Dec 2018
Minified
Minified + Gzipped
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
4.2%
12,919
Compared to previous day
Last week
8.2%
89,753
Compared to previous week
Last month
163.1%
308,926
Compared to previous month
Last year
33.8%
1,484,479
Compared to previous year
Optimized and powerful regexes for JavaScript
In ES5, matching literal regexes with other regex in medium complexity code is highly risky.
In ES6 it is practically impossible.
For this reason, as of v1.0 JS_REGEX_P
is deprecated and will be removed in the next minor version.
JS_REGEX
will be maintained, but its use should be limited to complement other utilities, such as skip-regex, which uses a customized version of JS_REGEX
to identify regular expresions reliably.
The minimum supported version of NodeJS now is 6.14 (oldest maintained LTS version w/fixes).
1npm install perf-regexes --save 2# or 3yarn add perf-regexes
In the browser, this loads perf-regexes in the global R
object:
1<script src="https://unpkg.com/perf-regexes/index.min.js"></script>
All of these regexes recognize Win/Mac/Unix line-endings and are ready to be used, but you can customize them using the RegExp
constructor and the source
property of the desired regex.
HTML:
Name | Flags | Matches |
---|---|---|
HTML_CMNT | g | Valid HTML comments, according to the SGML standard. |
JavaScript:
Name | Flags | Matches |
---|---|---|
JS_MLCMNT | g | Multiline JS comment, with support for embedded '/*' sequences. |
JS_SLCMNT | g | Single-line JS comments, not including its line-ending. |
JS_DQSTR | g | Double quoted JS string, with support for escaped quotes and line-endings. |
JS_SQSTR | g | Single quoted JS string, with support for escaped quotes and line-endings. |
JS_STRING | g | Combines JS_SQSTR and JS_DQSTR to match single or double quoted strings. |
JS_REGEX | g | Regex. Note: The result must be validated. |
JS_REGEX_P | g | Deprecated, do not use it. |
Selection of lines:
Name | Flags | Matches |
---|---|---|
EMPTY_LINES | gm | Empty line or line with only whitespace within, including its line-ending, if it has one. |
NON_EMPTY_LINES | gm | Line with at least one non-whitespace character, including its line-ending, if it has one. |
TRAILING_WS | gm | The trailing whitespace of a line, without including its line-ending. |
OPT_WS_EOL | g | Zero or more blank characters followed by a line-ending, or the final blanks, if the (last) line has no line-ending. |
EOL | g | Line-ending of any type |
Because the 'g'
flag, always set lastIndex
or clone the regex before using it with the exec
method.
Using only one regex, this simple example will...
1const R = require('perf-regexes') 2 3const cleaner = (text) => text.split(R.OPT_WS_EOL).filter(Boolean).join('\n') 4 5console.dir(cleaner(' \r\r\n\nAA\t\t\t\r\n\rBB\nCC \rDD ')) 6// ⇒ 'AA\nBB\nCC\nDD'
Use the previous function to cleanup HTML text:
1const htmlCleaner = (html) => cleaner(html.replace(R.HTML_CMNT, '')) 2 3console.dir(htmlCleaner( 4 '\r<!--header--><h1>A</h1>\r<div>B<br>\r\nC</div> <!--end-->\n')) 5// ⇒ '<h1>A</h1>\n<div>B<br>\nC</div>'
1const R = require('perf-regexes') 2 3const normalize = (text) => text.split(R.EOL).join('\n') 4 5console.dir(normalize('\rAA\r\r\nBB\r\nCC \nDD\r')) 6// ⇒ '\nAA\n\nBB\nCC \nDD\n'
1const toSingleQuotes = (text) => text.replace(R.JS_STRING, (str) => { 2 return str[0] === '"' 3 ? `'${str.slice(1, -1).replace(/'/g, "\\'")}'` 4 : str 5}) 6 7console.log(toSingleQuotes(`"A's" 'B' "C"`)) 8// ⇒ 'A\'s' 'B' 'C'
With the arrival of ES6TL and new keywords, finding literal regexes with another regex is not viable, you need a JS parser such as acorn or a specialized one such as skip-regex to do it correctly.
This is a very basic example that uses skip-regex:
1import R from 'perf-regexes' 2import skipRegex from 'skip-regex' 3 4/** 5 * Source to match quoted string, comments, and slashes. 6 * Captures en $1 the slash 7 */ 8const reStr = `${R.JS_STRING.source}|${R.JS_MLCMNT.source}|${R.JS_SLCMNT.source}|(/)` 9 10/** 11 * Search regexes in `code` and display the result to the console. 12 */ 13const searchRegexes = (code) => { 14 15 // Creating `re` here keeps its lastIndex private 16 const re = RegExp(reStr, 'g') 17 let match = re.exec(code) 18 19 while (match) { 20 if (match[1]) { 21 const start = match.index 22 const end = skipRegex(code, start) 23 24 // skipRegex returns start+1 if this is not a regex 25 if (end > start + 1) { 26 console.log(`Found "${code.slice(start, end)}" at ${start}`) 27 } 28 re.lastIndex = end 29 } 30 match = re.exec(code) 31 } 32} 33 34const code = ` 35const A = 2 36const s = '/A/' // must not find /A/ 37 38const re1 = /A/g // regex 39re1.lastIndex = 2 /A/ 1 // must not find /A/ 40 41/* /B/ // must not find /B/ 42*/ 43const re2 = /B/g // regex 44re1.exec(s || "/B/") // must not find /B/ 45` 46 47searchRegexes(code) 48// output: 49// Found "/A/g" at 74 50// Found "/B/b" at 210
The previous code does not support ES6TL, but it works quite well on ES5 files and is very fast.
For a more complete example of using perf-regexes, see js-cleanup, an advanced utility with support for ES6 that trims trailing spaces, compacts empty lines, normalizes line-endings, and removes comments conditionally.
ES6TLs are too complex to be identified by one single regex, do not even try.
I'm a full-stack developer with more than 20 year of experience and I try to share most of my work for free and help others, but this takes a significant amount of time and effort so, if you like my work, please consider...
Of course, feedback, PRs, and stars are also welcome 🙃
Thanks for your support!
The MIT License (MIT)
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 0/12 approved changesets -- score normalized to 0
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
58 existing vulnerabilities detected
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More