# parse-regexp

> parse a regexp string. `parse(reg_exp.toString()) == reg_exp`

Latest version **0.0.2** (published 2016-05-29) · MIT license · 0 weekly downloads

## Install

```sh
npm install parse-regexp
pnpm add parse-regexp
yarn add parse-regexp
bun add parse-regexp
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.2 |
| Published | 2016-05-29 |
| First published | 2012-10-24 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 2 |
| Author | 'Dominic Tarr' |
| Maintainers | dominictarr |

## Links

- npm: https://www.npmjs.com/package/parse-regexp
- Repository: https://github.com/dominictarr/parse-regexp
- Issues: https://github.com/dominictarr/parse-regexp/issues
- npm.io page: https://npm.io/package/parse-regexp

## Recent versions

- 0.0.2 (latest) — 2016-05-29
- 0.0.1 — 2012-10-24
- 0.0.0 — 2012-10-24

## README

# parse-regexp
parse a regexp string. `parse(reg_exp.toString()) == reg_exp`

<img src=https://secure.travis-ci.org/'Dominic Tarr'/parse-regexp.png?branch=master>

Put RegExps in your config files or, or use them as object keys!

```
  var rxparse = require('regexp-parse')
  rxparse('/whatever/m')

  => /whatever/m

```

If you are using this to parse user input I would recommend
first passing the regular expression through [safe-regex](https://github.com/substack/safe-regex)

## License

MIT

---
_Source: https://npm.io/package/parse-regexp · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._