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

mdjsx

v1.0.0-6

Published

CLI for rendering .mdx and .jsx files

Downloads

4

Readme

mdjsx

CLI for rendering .mdx & .jsx files

npm i -D mdjsx

Add run scripts to your package.json

"scripts": {
  "start": "mdjsx hello.mdx",
  "build": "mdjsx hello.mdx -d dist"
}

Usage

Development server

mdjsx hello.mdx

Static build

mdjsx hello.mdx --out-dir dist

HTML only build

mdjsx hello.mdx --out-dir dist --static

Options

  • -p --port: port number for development server
  • -o --open: automatically open development server in default browser
  • -c --config: path to config file
  • -s --static: renders HTML without client-side bundle.js
  • -d --out-dir: builds page to the given directory

MDX Format

MDX files combine markdown syntax with JSX. Each .mdx file can use front-matter to define default props and metadata used for static page generation.

Example .mdx file

---
title: Hello MDX
---

# Hello Markdown

<div>
  <h2>{props.title}</h2>
</div>

JSX Format

JSX files are rendered as pure React components, which allows for rapid prototyping without the need to setup a full React application. JSX files also use front-matter to define default props and metadata.

Example .jsx file

---
title: Hello JSX
---
<div>
  <h2>{props.title}</h2>
</div>

Configuration

A configuration file can be provided to add components and theme to scope.

// example config.js file
import * as Rebass from 'rebass'

const components = Rebass

const theme = {
  colors: {
    blue: '#07c',
    green: '#0f8'
  }
}

export default {
  components,
  theme
}

Use the --config flag to point to the configuration file.

mdjsx hello.mdx --config config.js

When a configuration file provides components in scope, they can be used in .mdx or .jsx files.

Example .jsx file

---
title: Hello JSX
---
<Box px={3} py={4} bg='blue' color='white'>
  <Heading>
    {props.title}
  </Heading>
</Box>

Provider

A wrapping higher-order component can be added to the config to provide data, layout, and other props to the rendered file.

// example config.js
import React from 'react'
import * as Rebass from 'rebass'

const components = Rebass

const provider = App => props => (
  <Rebass.Box px={3} py={4}>
    <App {...props} />
  </Rebass.Box>
)

export default {
  components,
  provider
}

MIT License