npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

super-regexp

v0.0.3

Published

Javascript Regular Expressions with Super Powers

Downloads

6

Readme

SRE: Super Regular Expression

Javascript Regular Expressions with Super Powers!

Status: Experimental

browser support

Why a Regular Expression framework?

When dealing with complex long regular expression there are a couple of thing you'd like and that Javascript currently does not provide:

  • Fragmenting the entire Reg Exp in smaller fragments.
  • Commenting / Documenting the Reg Exp.
  • Debugging helpers.

And that is exactly what SRE delivers.

Using it

npm install super-regexp

The mini framework is tested using Tape, run npm test to test it, and, inspect test.js to see what the Library can offer.

This is an extract of test.js


var SRE = require('super-regexp');

var s = SRE('Parse a root URL')
			.pat('^(http|https)?', 'Protocol. Its optional.')
			.pat('(://)?', 'Delimiter. Its optional.')
			.pat('(www)?', 'Optional www word')
			.pat('(?:\\.)?', 'Optional  dot.')
			.pat('([^\\.]*)', 'Domain name. Anything but a dot.')
			.pat('(?:\\.)', 'Dot.')
			.pat('([^$/]*)', 'Top level domain. Anything but a forward slash or the end of the string')
			.pat('(?:$|/$)', 'String end')
			.flags('ig');




test('SRE exec', function (t) {
    t.plan(6);

	var result = s.exec('http://www.domain.com');
	var expected = ['http://www.domain.com', 'http', '://', 'www', 'domain', 'com'];

    var i, r, e;
    for (i= 0; i < 6; i++ ) {
    	r = result[i];
    	e = expected[i];
    	t.equal(r, e);
    }
});

In the browser

<script src="dist/superre.js"></script>
<script>
var sre = SuperRegExp()
		.pat()
		.flags();
		
sre.exec(string);
</script>

Debugging

SRE has a debug(string) method that is built to help you debug your faulty Regular Expression. It will run exec(string) several times, adding the patterns one by one. This way you can isolate the issue to each patterns.

See test.js for more details.

Creating a Browser bundle

Install Browserify and run

browserify index.js --standalone SuperRegExp -o dist/superre.js

Creating a Browser test bundle

browserify test.js --standalone Super-RegExp -o dist/test_bundle.js

Or follow this tutorial

Contributing

This is an Open Source project so please, if you think there are improvements to be made in this library please submit a Pull Request or an Issue and we can discuss about it. The requirements of submitting code are that the new pieces are tested with Tape, and possibly in the future that they are linted.

TODO

  • Use Native RegExp and /as[\.]*d/.toString() to offer better integration.
  • Implement Named-capture. See nice implementation

License

The MIT License (MIT)

Copyright (c) 2014 Francisco Guijarro

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Copyright 2014 [email protected]