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

grunt-pathlint

v0.0.1

Published

A Grunt task for checking pathnames

Downloads

4

Readme

grunt-pathlint

A Grunt task for checking pathnames.

Travis Status David DM Status

Getting Started

If you haven't used grunt before, be sure to check out the Getting Started guide.

From the same directory as your project's Gruntfile and package.json, install this plugin with the following command:

npm install grunt-pathlint --save-dev

Once that's done, add this line to your project's Gruntfile:

grunt.loadNpmTasks('grunt-pathlint');

Inside your grunt.js file add a section named pathlint. This section specifies the tasks. Each task takes sources and options as parameters.

Parameters

sources src

This sets the path of the files and directories to be checked in this task.

Options

file option

A regular expression for a file name in a path matched by src. This validates only the full filename and not the full path of the file.

Default is /^.+$/ which allows all names.

dir option

A regular expression for a directory name in a path matched by src. A full path of a directory will be split and validated by it's containing directory names. For example the path foo/bar/baz/ will be split into foo, bar and baz. Each of these sections will be validated by this regular expression. It's not required to add any path seperators into the regular expression.

Default is /^.+$/ which allows all names.

Example

	pathlint {
		js: {
			src: ['js/src/**/*'],
			options: {
				file: /^([a-zA-Z0-9])+\.(js)$/,
				dir: /^([a-z0-9])+$/
			}
		},
		scss: {
			src: ['scss/**/*'],
			options: {
				file: /^(_?[a-z0-9]|-)+\.(scss)$/
				// Do not test for dirs here, so all pathes are valid...
			}
		}
	}

Contribution

Tests & Validation

Run grunt to lint and run the tests.

License

LICENSE (MIT)