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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mcshading

v1.0.7

Published

shade datapack namespaces/folders into others

Readme

mcshading

maven shading for datapacks and resource packs.

syncronously rewrites all references to one namespace to references to another in the contents of files and in their paths.

mcshading is pretty versitile, it can be run from the command line or from a javascript/typescript program and it can be used for more than just shading.

what mcshading does

here are some examples of how mcshading might change a datapack

# command: mcshading ./old ./new
# path:    ./old/functions/tick.mcfunction

advancement grant @a only old:very_old_advancement
kill @e[type=#old:very_old_type]

# path:    ./new/functions/tick.mcfunction

advancement grant @a only new:very_old_advancement
kill @e[type=#new:very_old_type]
# command: mcshading ./old ./new sub
# path:    ./old/functions/tick.mcfunction

advancement grant @a only old:very_old_advancement
kill @e[type=#old:very_old_type]

# path:    ./new/functions/sub/tick.mcfunction

advancement grant @a only new:sub/very_old_advancement
kill @e[type=#new:sub/very_old_type]

mcshading from the command line

install the module like this to use it in a global context

npm i -g mcshading

and then to use it as such

mcshading <source namespace> <destination namespace>

example:

mcshading datapack/data/foo other_datapack/data/bar bar_sub_folder/ foo_sub_folder/

(trailing slash is required!)

mcshading from javascript

install the module globally (recommended) or locally (no -g for locally)

npm i -g mcshading

and then use the module in one of two ways

const { shadeDatapack } = require('mcshading');
shadeDatapack('source', 'destination', 'more of the destination', 'more of the source');

// or

const mcshading = require('mcshading');
mcshading.shadeDatapack('source', 'destination', 'more of the destination', 'more of the source');

mcshading from typescript

install the module globally (recommended) or locally (no -g for locally)

npm i -g mcshading

and then use the module in one of two ways

import { shadeDatapack } from 'mcshading';
shadeDatapack('source', 'destination', 'more of the destination', 'more of the source');

// or

import * as mcshading from 'mcshading';
mcshading.shadeDatapack('source', 'destination', 'more of the destination', 'more of the source');