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

metadata-filter

v1.3.0

Published

A module for cleaning up artist, album, and song names.

Downloads

48

Readme

metadata-filter Test NPM Codacy Coverage

A module for cleaning up artist, album, and song names.

Installation

Install using npm

npm i metadata-filter

Include via CDN

<script src="https://unpkg.com/metadata-filter@latest/dist/filter.min.js"></script>

Usage

If you want to use this module in a project which is built with a bundler (e.g. webpack), you can use CommonJS-like or ES6 imports:

// CommonJS style
const MetadataFilter = require('metadata-filter');

// ES6 style
import * as MetadataFilter from 'metadata-filter';

MetadataFilter.removeRemastered(yourInput);

In a browser you can access to the module by using the global MetadataFilter object:

<!-- Assume you have `metadata-filter` module included with `script` tag -->
<script lang="javascript">
	MetadataFilter.removeRemastered(yourInput);
</script>

Single filter functions

You can call filter functions for basic, one-line filter functionality. These filter functions are intended to be used on a single field, such as an artist, album, or track.

However, it is possible (not officially supported) to use some of these on combined fields ("Artist - Song", "Artist - Album"), as in the third example below.

console.log(MetadataFilter.removeRemastered('Jane Doe (Remastered)')); // Jane Doe
console.log(MetadataFilter.removeVersion('Get Lucky (Album Version)')); // Get Lucky
console.log(
	MetadataFilter.youtube(
		'Car Bomb - Scattered Sprites (Official Music Video)'
	)
); // Car Bomb - Scattered Sprites

See src/functions.ts for more details.

Combine filter functions

You can also use multiple filter functions on a string at once by creating a MetadataFilter object which combines multiple functions from above, or by using one of the pre-existing filter objects.

First, create a filter set. This is a set of filter functions for different fields.

const filterSet = {
	track: [
		MetadataFilter.removeRemastered,
		MetadataFilter.fixTrackSuffix,
		MetadataFilter.removeLive,
	],
	album: [
		MetadataFilter.removeRemastered,
		MetadataFilter.fixTrackSuffix,
		MetadataFilter.removeLive,
	],
};

Then, construct a MetadataFilter using this filter set.

const filter = MetadataFilter.createFilter(filterSet);
console.log(filter.filterField('album', 'Nevermind (Remastered)')); // Nevermind
console.log(filter.filterField('track', 'In Bloom - Nevermind Version')); // In Bloom (Nevermind Version)

Predefined filters

There are also predefined filters available for easy access. For example, the above filter set can be acquired using createSpotifyFilter() function:

const filter = MetadataFilter.createSpotifyFilter();

See src/filters.ts for more details.

Extending filters

Finally, you can take existing MetadataFilter objects and extend them with another filter. This is done by providing the .extend() method with another MetadataFilter object.

const filter = MetadataFilter.createSpotifyFilter();

filter.extend(MetadataFilter.createAmazonFilter());
// This would also work: filter.extend(MetadataFilter.createFilter(filterSet));

console.log(
	filter.filterField('track', 'Seasons in the Abyss (Album Version)')
); // Seasons in the Abyss

As an alternative, you can use the .append() method to apply a filter set to an existing MetadataFilter object.

const filter = MetadataFilter.createFilter({ track: filterTrack });

filter.append({ artist: filterArtist });

Since these methods return a MetadataFilter instance, you can chain method calls.

const filter = MetadataFilter.createFilter({ track: filterTrack }).append({
	artist: filterArtist,
});

Development

# Install dev dependencies
> npm install

# Build the dist file
> npm run build

# Format files
> npm run format

# Lint source files
> npm run lint

# Run tests
> npm test

# Run tests with a coverage report
> npm run test-with-coverage

License

Licensed under the MIT License.