Add a Regex Tester tool
I maintainer di solito rispondono entro 1 giorno
@prakashNalla ci sta già lavorando.
Dal 22/10/2026.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 74/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- javascript, nextjs, tailwindcss, typescript
Direzione di ricerca
Start with lib/tools.ts and the complete tool structure in app/(tools)/base64/; also read the README’s “Add a tool” section. Implement and test pure logic in lib/regex-utils.ts and lib/__tests__/regex-utils.test.ts, then add the route, client UI, registry entry, and checklist items. Done means the listed tests and UI criteria pass and npm run lint && npm run test && npm run build succeeds.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Test a JavaScript regular expression against sample text, with highlighted matches, capture groups and a replace preview, all in the browser.
Route: /regex-tester
Suggested registry values: title Regex Tester, tagline Patterns, heroHeading Regex Tester with heroDim "", features ["Live matches", "Flags", "Capture groups", "Named groups", "Replace"].
Core logic in lib/regex-utils.ts
compileRegex(pattern, flags)returning{ ok: true, regex } | { ok: false, error }with a friendly messagefindMatches(regex, text, { limit = 1000 })returning{ matches: [{ text, index, end, groups, named }], truncated }. Always iterate a global copy of the regex and advancelastIndexon zero-length matches, so patterns likea*or^can't loop forever.replacePreview(regex, text, replacement)supporting$1and$<name>
v1 scope
- Pattern input with flag toggles (
g,i,m,s,u,y) - Test text with highlighted matches
- A match table with capture groups
- Replace preview
- Debounced input and a size cap on the test text (for example 100 KB)
Known limitation: catastrophic backtracking (for example (a+)+$ on a long string) can still freeze the tab in v1. Running matches in a Web Worker with a timeout is a good follow-up.
Out of scope for v1: a regex explainer, saved patterns, other regex flavours.
Where to look
lib/tools.ts(the registry and theToolinterface)app/(tools)/base64/(a complete tool to copy the structure from)- The "Add a tool" section of the README
Acceptance criteria
- Tests: zero-length patterns terminate, named groups are returned, invalid patterns and flags give
ok: false, hitting the limit setstruncated, and replacement with$1and$<name>works - UI as scoped above
- The standard new-tool checklist below is complete
Standard new-tool checklist
Everything (home grid, metadata, JSON-LD, OG image, sitemap, manifest, command palette) is driven by the registry in lib/tools.ts, so a new tool is mostly one registry entry plus a route.
- Add an entry to
TOOLSinlib/tools.tsfilling every field of theToolinterface (lib/tools.ts:19-52). UseapplicationCategory: "DeveloperApplication", reuse theCTA_PROJECTS/CTA_CONTACTconstants for the CTA links, and setsitemapPriority: 0.9like the other tools. - Pick
accentVarfrom the accent variables inapp/globals.css(the list is under "Adding a tool" in CONTRIBUTING.md). Take one that no tool uses yet, or the one the fewest tools have if they're all taken. Don't use--rose, it's the color of error messages. SetaccentHexto that variable's dark-theme value.heroDimmust be""or a substring ofheroHeading. - Write 3 or 4 FAQs (3 renders as a 3-column grid, see
components/shared/ToolPageLayout.tsx:25). KeepmetaTitleunder 60 characters andmetaDescriptionaround 150 to 160. - Keep
featuresandogDescriptionto plain Latin text and punctuation. The social card font is a subset with no arrow or symbol glyphs (lib/og.tsx:33-36). - Create
app/(tools)/<slug>/page.tsx,<Name>Client.tsx(with"use client"), andopengraph-image.tsx. Copypage.tsxandopengraph-image.tsxfromapp/(tools)/base64/and change the slug. - Put all pure logic in
lib/<name>.ts(no React, no DOM) with tests inlib/__tests__/<name>.test.ts. Tests can import with@/like the app does (vitest.config.tshas the alias). - Nothing leaves the browser: no network calls with user input, no analytics, no third-party scripts (the CSP in
middleware.tsblocks external scripts anyway). - Reuse shared pieces:
CopyButton,useToast, and optionallyuseRegisterCommandsfor command palette actions (example inapp/(tools)/base64/Base64Client.tsx:43-53). - Every input has a visible label or an
aria-label, the tool works with the keyboard alone, and it looks right in both light and dark themes. - Add the tool to the "Which tool?" dropdown in
.github/ISSUE_TEMPLATE/bug_report.yml. -
npm run lint && npm run test && npm run buildpasses.
One new tool per contributor, so more people get a chance. Add your registry entry at the end of TOOLS and rebase on develop before asking for review, since other new tools will touch the same file.
Want to work on this? Comment below and I'll assign it to you. Please take one issue at a time, branch off develop, and open your PR against develop with Closes #85 in the description.
- Lingua principale
- TypeScript
- Stelle
- 1
- Fork
- 9
- Merge medio
- 7h 34m
- PR unite (30g)
- 146
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di codercops/toolbelt
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Cron explainer says "on weekdays" for `0 0 1-31 * 1-5`, but the next runs include weekendsForse già presa @Saifjafri212213 l’ha presa oggi. Apertabug hacktoberfest help wanted
codercops/toolbelt#329 · 2 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
UUID generator's v7 batch comes out in random order instead of time orderForse già presa @omisha123 l’ha presa oggi. Apertabug good first issue hacktoberfest
codercops/toolbelt#316 · 3 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Invoice generator shows a subtotal of -$0.00 when the line items cancel outForse già presa @shresthgoel77-png l’ha presa 1 giorno fa. Apertabug good first issue hacktoberfest
codercops/toolbelt#315 · 2 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
JSON formatter's "Did you mean" hint reads inside strings, so a missing comma near a URL says to remove commentsForse già presa @kachamsiddarth l’ha presa oggi. Apertabug good first issue hacktoberfest
codercops/toolbelt#314 · 2 commenti · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di codercops/toolbelt
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
farion1231/cc-switch#8829 ·
I maintainer di solito rispondono entro 1 giorno
-
[core-client] Remove unused hand-maintained transport helpers after the definition-table cutoverApertadoc-audit enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100