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

@acta/path-matcher

v1.0.4

Published

Compile a regex matcher from a path template and test real paths against it.

Downloads

11

Readme

Path-Matcher @acta/path-matcher

To compile a regex matcher from a path template and test paths against a regex matcher. This is meant to be used as an utilit for a router.

Table of Contents

Basic use case

Test a path against a template with testPath( path, template ). If the path matches with the template, an object with the name, the pathname and the segment values is returned. Otherwise, the test returns false.

import pathMatcher from '@acta/path-matcher';

// Strict template
pathMatcher.testPath('/foo/bar', '/foo/bar');
/**
  {
    name: '/foo/bar', <= the template is unnamed
    pathname: '/foo/bar',
    segments: {},
    template: '/foo/bar',
  }
 */

// Template with variable segment
pathMatcher.testPath('/foo/bar', '/foo/{baz}')
/**
  {
    name: '/foo/{baz}',
    pathname: '/foo/bar',
    segments: { baz: 'bar' }, <= the value for the segment 'baz'
    template: '/foo/{baz}',
  }
 */

// Template with optional segment
pathMatcher.testPath('/foo', '/foo/{bar?}')
/**
  {
    name: '/foo/{bar?}',
    pathname: '/foo',
    segments: { bar: null }, <= note the optional segment at null
    template: '/foo/{bar?}',
  }
 */

// No match
pathMatcher.testPath('/foo/bar', '/bar/foo'); // false

Store compiled templates

You can store templates in the pathMatcher object. They will be compiled for later use.

import pathMatcher from '@acta/path-matcher';

// As a simple string
pathMatcher.addTemplate('/foo/{bar?}');

// As a template with meta data
pathMatcher.addTemplate({
  name: 'foobar',
  paramsChecks: {
    bar: /[0-9]?/
  },
  template: '/foo/{bar?}'
});

The compiled template will be accessible in pathMatcher.compiledTemplates.

Test against a compiled template

When a template has been stored, you can test a path against it.

import pathMatcher from '@acta/path-matcher';

pathMatcher.testPathAgainstCompiledTemplate('foobar', 'foo/123');
/**
  {
    name: 'foobar', <= now the template is named
    pathname: 'foo/baz',
    segments: {
      bar: '123'
    },
    template: '/foo/{bar?}',
  }
 */

This is more of an internal method used to find a template, but you can use it to build a router.

Check if a path matches a stored template

import pathMatcher from '@acta/path-matcher';

// Add a simple template
pathMatcher.addTemplate('/foo/bar/{baz?}');

// Add the template with meta data
pathMatcher.addTemplate({
  name: 'foobar',
  paramsChecks: {
    bar: /[0-9]?/
  },
  template: '/foo/{bar?}'
});

// Find the path
pathMatcher.findPath('foo/123');
/**
  {
    name: 'foobar',
    pathname: 'foo/baz',
    segments: {
      bar: '123'
    },
    template: '/foo/{bar?}',
  }
 */

// Find an unknown path
pathMatcher.findPath('bar/123');
/**
  false
 */

Dev scripts

Scripts :

  • npm run dev to dev (build, test and watch)
  • npm run build to build the production version
  • npm run release to release a new version. Relies on release-it for deployments.

To develop in local using the package from another application or package, go for a symlink: npm link /the/absolute/path/url.

To publish: npm publish --access=public.