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

@djs-commands/jsx

v2.0.1

Published

JSX runtime + components for djs-commands — Components V2 expressed as JSX

Readme

@djs-commands/jsx

JSX runtime + Components V2 component set for @djs-commands/core.

📘 Full documentation: https://djscommands.deoxy.dev/components-v2

Write Discord Components V2 messages as JSX, compile to discord.js builders:

import { Container, Section, TextDisplay, Button, render } from "@djs-commands/jsx";
import { MessageFlags } from "discord.js";

await interaction.reply({
	flags: MessageFlags.IsComponentsV2,
	components: render(
		<Container accentColor={0x5865f2}>
			<TextDisplay># Welcome</TextDisplay>
			<Section accessory={<Button style="primary" customId="ok" label="OK" />}>
				Click the button to continue.
			</Section>
		</Container>
	),
});

Install

bun add @djs-commands/jsx

In your tsconfig.json:

{
	"compilerOptions": {
		"jsx": "react-jsx",
		"jsxImportSource": "@djs-commands/jsx"
	}
}

That's it — no Babel, no SWC, no React. The TypeScript compiler (and Bun's transpiler) emits import { jsx } from "@djs-commands/jsx/jsx-runtime" automatically.

Components

Display: <Container>, <Section>, <TextDisplay>, <MediaGallery>, <Separator>, <File>, <Thumbnail>

Forms: <ActionRow>, <Button> (primary/secondary/success/danger/link/premium), <Modal>, <TextInput>, <RadioGroup>, <CheckboxGroup>

Renderers: render(tree) for messages, renderModal(tree) for interaction.showModal.

The full surface — every component, side-by-side JSX vs. function examples, modal forms — is on the Components V2 docs page.

No JSX? Use the function fallback

If you can't (or won't) enable JSX in your project, every component has a function-form sibling re-exported from @djs-commands/core (e.g. container, section, textDisplay, button). They return the same discord.js builders, so you can mix the two freely.

import { button, container, section, textDisplay } from "@djs-commands/core";

License

MIT · Issues + discussions on GitHub.