Regex Cheat Sheet: Command Line vs Online

Use a command-line regex cheat sheet only when its documented dialect matches the program that will execute the pattern; use an online JavaScript regex cheat sheet when the code runs through JavaScript RegExp.

Regex syntax belongs to the program that evaluates it, not automatically to the shell. A command that invokes GNU grep with PCRE, a Python one-liner, and node -e can each use a different dialect. The JavaScript-specific Regex Cheat Sheet is therefore an online reference for ECMAScript RegExp, not a universal sheet for grep, sed, Perl, Python, .NET, Java, RE2, or POSIX expressions.

What each option is actually for

The practical difference is not simply online versus command line. It is the documented dialect, the runtime that executes the pattern, and whether the reference is being used for lookup or behavior testing.

Option	What it answers	Best fit	Main limitation
Command-line reference or local manual	Which syntax the installed program accepts	Building a grep, sed, awk, or runtime command	Options and regex behavior can vary by program and version
Online JavaScript cheat sheet	What a JavaScript RegExp token means	Browser or Node.js JavaScript code	JavaScript syntax is not portable to every command-line engine
Local engine help	Which flags and modes the installed command supports	Verifying the exact command before running it	Help output may not provide a complete syntax guide
Live JavaScript tester	How a pattern behaves on supplied text	Checking matches and capture groups	A successful sample does not guarantee compatibility in every runtime

On GNU grep, for example, grep -E selects extended regular-expression behavior, while grep -P selects PCRE. Another grep implementation may not offer -P at all. Shell quoting can protect a pattern from the shell, but it cannot translate one regex dialect into another.

Identify the regex dialect before choosing syntax

Record the executable and its regex mode before looking up a token. The same command-line workflow can require different references depending on which program receives the pattern.

• Shell utilities: A grep, sed, or awk implementation may use POSIX basic expressions, POSIX extended expressions, PCRE, or an implementation-specific variation.
• Language runtimes: Python, Perl, Java, .NET, and RE2-based tools have distinct regex syntax, feature sets, and Unicode behaviors.
• JavaScript: A browser expression or a Node.js call to RegExp uses JavaScript RegExp syntax. A command launched from a terminal is still JavaScript when node -e executes a RegExp expression.

Do not infer the dialect from the interface used to write the pattern. A token copied from an online JavaScript table may be rejected by a command-line utility or carry different semantics there. Conversely, a PCRE pattern placed in JavaScript code is not made valid merely because it works in a terminal tool.

Use a command-line regex reference without crossing dialects

1. Identify the exact command and mode. Check the installed program’s version and help output before consulting a syntax sheet. For GNU grep, distinguish grep -E from grep -P; do not assume those modes accept identical patterns.
2. Open documentation for that engine. Use a POSIX expression reference for a POSIX ERE workflow and PCRE documentation for a PCRE workflow. If the command runs JavaScript through node -e, use the JavaScript RegExp reference instead.
3. Prepare a small known fixture. For example, printf 'id=42\nid=abc\n' creates two lines with one numeric value and one nonnumeric value.
4. Run a narrow search. With a POSIX-compatible grep, printf 'id=42\nid=abc\n' | grep -nE 'id=[0-9]+' applies an extended expression and prints line numbers. The pattern is designed to select the first fixture line rather than the second.
5. Quote the pattern for the shell. Single quotes keep shell expansion from altering regex characters. That protection does not add unsupported tokens or convert between dialects.
6. Check representative cases and engine settings. Include both matching and nonmatching text, then consult the installed documentation for Unicode, case-sensitivity, and program-specific options. A result from one command version does not establish behavior on another platform.

Find and copy JavaScript RegExp tokens online

1. Enter the token or concept. Search for a symbol such as \d or a term such as “lookbehind,” “Unicode,” “lazy,” or “named.”
2. Narrow the results by category. Choose from characters, character classes, groups and references, quantifiers, assertions, or flags. Search terms and category filters combine, the displayed count covers the complete matching set, and an empty result produces an explicit empty state.
3. Review the selected row. Each row contains a category, exact token, concise meaning, and JavaScript example. The example is written as a JavaScript regular-expression literal so its slash delimiters and flags remain visible.
4. Select Copy on the desired row. The clipboard receives only the exact token in the Token column, not the category, explanation, example, delimiters, or example flags.
5. Place the token into your existing pattern. Add the delimiters and flags required by your code separately. For example, a copied property escape still needs Unicode-aware mode, and the u and v flags cannot be combined on the same RegExp.
6. Handle the clipboard status accurately. Browser clipboard permission can be denied, in which case the tool reports a recoverable error rather than claiming success. Changing the search or category invalidates an older copy job and clears its status, while only the newest copy attempt may publish success or failure.

The reference contains 44 selected entries across the six categories, so it is a focused lookup aid rather than a complete language specification. Search and filtering run entirely in the current browser tab. No query, selected category, copied token, or other input is uploaded to Lizely or another service.

Tokens that expose dialect mismatches

Some tokens look portable but carry JavaScript-specific rules. Check the following distinctions before inserting a symbol into a pattern:

JavaScript token	Meaning	Boundary to check
\d	Matches an ASCII digit from 0 through 9	It is not a shortcut for every Unicode decimal digit
\w	Primarily covers ASCII letters, ASCII digits, and underscore	It has a documented Unicode-aware case-folding nuance when the i and u flags are combined
\p{Letter}	Matches characters with the Unicode Letter property	Unicode-aware mode is required
\P{Letter}	Matches the complement of the Unicode Letter property	Unicode-aware mode is required
(?<=...) and (?<!...)	Positive and negative lookbehind	They inspect preceding text without consuming that text
(?:...)	Non-capturing group	It controls grouping and precedence without adding a capture slot
\1 and \k<name>	Numbered and named backreferences	They refer to previously captured text and are not interchangeable
x|y	Alternation	The pattern matches either branch
A trailing ? after a quantifier	Lazy quantifier behavior	It does not make the underlying token optional

Flags also change behavior. The s flag lets dot match line terminators, while m changes how ^ and $ handle line boundaries. The g flag enables global matching and affects lastIndex in stateful operations; y requires a match at lastIndex; and d exposes match indices. The u flag provides Unicode-aware matching and code-point escapes, while v enables UnicodeSets behavior. JavaScript does not allow u and v together.

Test the pattern in the runtime that matters

A cheat sheet is a syntax reference, not a regex validator, security analyzer, compatibility database, or guarantee that a pattern is efficient. Test real patterns against representative inputs and avoid uncontrolled backtracking on untrusted text. For JavaScript, the Regex Tester should be used when pattern behavior matters; the guide on checking a regex pattern in JavaScript provides a more systematic validation workflow. When code targets a particular browser, embedded runtime, or older Node.js version, verify that environment’s feature support.

For a command-line pattern, run the actual installed command against a controlled fixture and review its documented mode. For JavaScript, use the MDN JavaScript regular expression syntax cheat sheet and the MDN RegExp reference for engine-specific syntax. The Regex Cheat Sheet entries are checked against ECMAScript’s RegExp pattern grammar and cross-checked against MDN’s JavaScript documentation.