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

lets-talk-about

v0.4.0

Published

Easily create slides from Markdown. Customize your slides with HTML and CSS. Host your slides for free on GitHub Pages.

Readme

lets-talk-about

Create beautiful slide presentations from Markdown.

Quick Start

npx lets-talk-about init my-talk
cd my-talk
npm install
npx lets-talk-about dev

Commands

| Command | Description | |---|---| | lets-talk-about init [name] | Scaffold a new presentation project | | lets-talk-about dev | Start dev server with hot reload | | lets-talk-about build | Build for production | | lets-talk-about deploy | Deploy to GitHub Pages |

Slide Format

Write slides in a single Markdown file. Each --- starts a new slide:

---
title: My Presentation
---

# First Slide

Content here

---

# Second Slide

- Point 1
- Point 2

---
type: section

# Section Divider

Per-slide Options

Add options at the top of a slide, right after the --- separator, followed by a blank line:

---
type: section

# Section Title

---
build: true

## Revealed Items

- First
- Second

Each --- starts a new slide. Options at the top clearly belong to that slide.

You can also use the legacy format with options in a separate --- block (backward compatible):

---
type: section
---

# Section Title

Available options:

| Option | Values | Description | |---|---|---| | type | section | Section divider slide with theme background | | build | true | Progressive reveal of list items | | background | /assets/bg/1.jpg | Background image path | | cover | true | Use cover instead of contain for background | | class | any CSS class | Add custom class to the slide |

Code Blocks

Fenced code blocks support syntax highlighting, line numbers, and line highlighting via the info string:

```js
const plain = 'syntax highlighting only';
```

```js linenums
const numbered = 'with line numbers';
```

```js h2
const line1 = 'normal';
const line2 = 'highlighted';
const line3 = 'normal';
```

```js linenums h2 h4-6
function example() {
  const a = 1;       // line 2: highlighted
  const b = 2;
  const c = 3;       // lines 4-6: highlighted
  const d = 4;
  const e = 5;
}
```

| Token | Description | |---|---| | linenums | Show line numbers | | hN | Highlight line N (e.g. h3) | | hN-M | Highlight lines N through M (e.g. h4-6) |

Combine freely: ```js linenums h1 h5-7

Templates

Templates let you arrange content within a slide using named slots. Use ::slotname:: delimiters to define slots:

---
template: two-column

## Left Column

- Item A
- Item B

::right::

## Right Column

- Item C
- Item D

Content before any ::slotname:: delimiter becomes the default slot.

Built-in Templates

| Template | Slots | Description | |---|---|---| | default | default | Standard slide (no change) | | two-column | default, right | Side-by-side flex columns | | title-content | title, default | Title area with border, content below |

Custom Templates

Define custom templates in lets-talk-about.config.js:

export default {
  templates: {
    'my-layout': (slots) => `
      <div class="sidebar">${slots.sidebar || ''}</div>
      <div class="main">${slots.default || ''}</div>
    `,
  },
};

Each template is a function that receives an object of rendered HTML slots and returns HTML.

Layouts

Layouts add persistent elements (header, footer, watermark) to every slide:

export default {
  layout: {
    header: '<span>My Talk</span>',
    footer: '<span>{{slideNumber}} / {{totalSlides}}</span>',
    watermark: '<span>DRAFT</span>',
  },
};

Use {{slideNumber}} and {{totalSlides}} placeholders for dynamic numbering.

Function Layout

For dynamic layouts, use a function:

export default {
  layout: (slideNumber, totalSlides) => ({
    footer: `<span>${slideNumber} / ${totalSlides}</span>`,
  }),
};

Theme Customization

Config Colors

Override CSS variables in lets-talk-about.config.js:

export default {
  theme: {
    colorTheme: '#e44',
    colorBackground: '#1a1a2e',
  },
};

Custom CSS

export default {
  styles: './custom.css',
};

Full Override

Import only the JS engine:

import { init } from 'lets-talk-about/client/slides';

Deployment

The scaffolded project includes a GitHub Actions workflow that builds and deploys your slides to GitHub Pages.

Setup

  1. Push your project to GitHub
  2. Go to your repo's Settings > Pages
  3. Under Build and deployment > Source, select GitHub Actions

The workflow triggers on pushes to the main branch. If your default branch has a different name, update branches: in .github/workflows/deploy.yml.

Custom Domain

To use a custom domain, add a CNAME file to your project root containing the domain:

my-slides.example.com

The deploy workflow automatically detects the CNAME file and adjusts the base path — no manual configuration needed.

License

MIT