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

@lilithmod/composition

v1.0.0-alpha.3

Published

Write complex Minecraft chat components in Typescript using tagged template literals.

Downloads

3

Readme

Composition

Are you tired of writing:

let component = {
    text: "Hello, ",
    color: "red",
    italic: true,
    extra: [
        {
            text: "Wor",
            color: "green",
            hoverEvent: {
                action: "show_text",
                value: {
                    text: "Nested component ",
                    color: "red",
                    extra: [
                        {
                            text: "again",
                            bold: true
                        }
                    ]
                }
            },
            extra: [
                {
                    text: "ld",
                    color: "dark_green"
                }
            ]
        },
        {
            text: "!!",
            underlined: true
        }
    ]
}

Composition lets you write the following:

c`Hello, ${
    green`Wor${darkGreen`ld`}`.hover(red`Nested component ${bold`again`}`)
}${underlined`!!`}`.red().italic().json()

...which is just a little more ergonomic. To make it even more concise, you can use Notchian color codes in every segment:

c`&c§oHello, ${
    hover`${c`&cNested component ${c`&lagain`}`} &aWor${c`&2ld`}`
}${underlined`!!`}`.red().italic().json() // Both & and § work

You can also use a minimal builder syntax if you want:

new TextComponentBuilder("This is a blue link!")
    .link('https://example.com')
    .underlined()
    .blue()
    .extra(
        new TextComponentBuilder(" (and this is some other text)")
            .gray()
            .underlined(false)
    )
    .json()

There are also some cool shortcut template literals for writing translation components or click/hover events:

t`translation.key.goes.here ${'and here'} ${'are as many subsitutions'} ${'as you want'}

${'without restrictions on whitespace'}`

link`${'https://any-url-goes.here'} Text content for your link`
// For every one of these shortcuts that needs one tag as a special parameter, the first space
// following it is removed for spacing reasons.

And finally, functions for the rest of the weird chat components.

k('forward') // keybind with no "key." necessary

score('player', 'objective', 'value') // this is up to you to figure out

sel('@a') // selector