Version 1.0.0

@stackline/regex-parser

A module that parses a string as regular expression and returns the parsed value.

Independent maintenance of regex-parser 2.3.1. Original authors and licenses are retained.

Installation

# Preserve existing imports with an npm alias
npm install regex-parser@npm:@stackline/regex-parser@1.0.0
# Or use the scoped package name in your imports
npm install @stackline/regex-parser@1.0.0

Node.js: See compatibility notes. Read the compatibility and maintenance notes before migrating.

Usage and API

The reference below may retain upstream package names. Use the alias installation above to run those imports with this Stackline release.

regex-parser

A module that parses a string as regular expression and returns the parsed value.

:cloud: Installation

# Using npm
npm install --save regex-parser

# Using yarn
yarn add regex-parser

:clipboard: Example

// Dependencies
var RegexParser = require("regex-parser");

console.log(RegexParser("/^hi$/g"));
// => /^hi$/g

:question: Get Help

There are few ways to get help:

Please post questions on Stack Overflow. You can open issues with questions, as long you add a link to your Stack Overflow question.
For bug reports and feature requests, open issues. :bug:
For direct and quick help, you can use Codementor. :rocket:

:memo: Documentation

`RegexParser(input)`

Parses a string input.

Params

String input: The string input that should be parsed as regular expression.

Return

RegExp The parsed regular expression.

:yum: How to contribute

Have an idea? Found a bug? See how to contribute.

:sparkling_heart: Support my projects

I open-source almost everything I can, and I try to reply to everyone needing help using these projects. Obviously, this takes time. You can integrate and use these projects in your applications for free! You can even change the source code and redistribute (even resell it).

However, if you get some profit from this or just want to encourage me to continue creating stuff, there are few ways you can do it:

Starring and sharing the projects you like :rocket:
—I love books! I will remember you after years if you buy me one. :grin: :book:
—You can make one-time donations via PayPal. I'll probably buy a ~~coffee~~ tea. :tea:
—Set up a recurring monthly donation and you will get interesting news about what I'm doing (things that I don't share with everyone).
Bitcoin—You can send me bitcoins at this address (or scanning the code below): 1P9BRsmazNQcuyTxEqveUsnf5CERdq35V6

Thanks! :heart:

:scroll: License

Upstream issues and maintenance review

Upstream origin and triage

Original package: regex-parser@2.3.1
Repository: https://github.com/IonicaBizau/regex-parser.js
Source commit: https://github.com/IonicaBizau/regex-parser.js/commit/455a3b0e259b4b970e331ae9d41663718b2ae34e
Source directory: .
npm tarball: https://registry.npmjs.org/regex-parser/-/regex-parser-2.3.1.tgz
SHA512 integrity: sha512-yXLRqatcCuKtVHsWrNg0JL3l1zGfdXeEvDa0bdu4tCDQw0RpMDZsqbkyRTUnKMR0tXF627V2oEWjBEaEdqTwtQ==
npm last-release age selects maintenance scope; it does not imply no ongoing source development.

Reviewed issues

Primary-source snapshot: 2026-09-29T00:21:42.769891+00:00. Most recently updated 100 open and 30 closed issue/PR entries; PRs removed. This is triage evidence, not a claim of exhaustive review.

Maintenance adoption with preserved runtime payload. No runtime defect correction is claimed. Reports remain visible for subsequent targeted reproduction.

The structured snapshot in .stackline/issue-triage.json also records recently closed reports. Issues for unrelated packages in shared monorepositories were qualified as outside this fork’s runtime scope. No maintainer was contacted.

Parse delimiter/flag boundaries in linear work while preserving upstream semantics across 5,000 generated differential inputs. User-selected regular expressions retain their original semantics.

Release files and references

Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.