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

@bem/sdk.naming.cell.pattern-parser

v0.0.7

Published

Pattern parser

Downloads

107

Readme

naming.cell.pattern-parser

Parser for the path pattern from a preset with a naming convention.

This is an internal package that is used in the @bem/sdk.naming.cell.stringify and @bem/sdk.naming.cell.match packages.

NPM Status

Introduction

The tool parses a pattern and creates an array with separate elements from the pattern.

The pattern describes the file structure organization of a BEM project. For example, the ${layer?${layer}.}blocks/${entity}.${tech} pattern matches the file path: my-layer.blocks/my-file.css.

Note. If you don't have any BEM projects available to try out the @bem/sdk.naming.cell.stringify package, the quickest way to create one is to use bem-express.

Try pattern-parser

An example is available in the RunKit editor.

Quick start

Attention. To use @bem/sdk.naming.cell.pattern-parser, you must install Node.js 8.0+.

In this quick start you will learn how to use this package to parse the path pattern from the origin preset.

To run the @bem/sdk.naming.cell.pattern-parser package:

  1. Install required packages.
  2. Create a parse() function.
  3. Parse the path pattern.

Installing required packages

Install the following packages:

To install the packages, run the following command:

$ npm install --save @bem/sdk.naming.cell.pattern-parser @bem/sdk.naming.presets

Creating a parse() function

Create a JavaScript file with any name (for example, app.js) and insert the following:

const parse = require('@bem/sdk.naming.cell.pattern-parser');

After that you can use the parse() function to parse a path pattern.

Parsing the path pattern from the origin preset

To parse a pattern, use the created function.

The pattern from the origin preset is equal to ${layer?${layer}.}blocks/${entity}.${tech}. Parse this pattern.

const originNaming = require('@bem/sdk.naming.presets/origin');

parse(originNaming.fs.pattern);
// => ['', ['layer', '', 'layer', '.'], 'blocks/', 'entity', '.', 'tech']

RunKit live example

API reference

parse()

Parses a path pattern into array representation.

/**
 * @param {string} pattern — Template-string-like pattern that describes
 *                           the file structure organization of a BEM project.
 * @returns {Array} — Array with separated elements from the pattern.
 */
parse(pattern);