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

@wtfb/cli

v1.0.1

Published

WTFB CLI - Validation and export tools for creative projects

Readme

@wtfb/cli

Validation and export tools for creative projects

Part of the Words To Film By ecosystem.


Installation

npm install -g @wtfb/cli

Usage

# Validate all project files
wtfb validate

# Validate specific types
wtfb validate --fountain    # Fountain files only
wtfb validate --markdown    # Markdown files only
wtfb validate --spelling    # Spell check only

# Export screenplay to PDF
wtfb export-pdf

# Export with specific output path
wtfb export-pdf my-script.fountain -o exports/final.pdf

# Export to Final Draft XML
wtfb export-fdx

# Export to HTML preview
wtfb export-html

# Skip pre-flight validation
wtfb export-pdf --no-validate

# Show CLI info
wtfb info

Commands

wtfb validate

Runs validation across your project files:

| Flag | Description | |------|-------------| | -f, --fountain | Validate Fountain files only | | -m, --markdown | Validate Markdown files only | | -s, --spelling | Run spell check only | | --fix | Auto-fix issues where possible |

wtfb export-pdf [file]

Export Fountain screenplay to industry-standard PDF.

| Option | Description | |--------|-------------| | -o, --output <path> | Custom output path | | --no-validate | Skip pre-flight validation |

wtfb export-fdx [file]

Export Fountain screenplay to Final Draft XML format.

| Option | Description | |--------|-------------| | -o, --output <path> | Custom output path | | --no-validate | Skip pre-flight validation |

wtfb export-html [file]

Export Fountain screenplay to HTML for web preview.

| Option | Description | |--------|-------------| | -o, --output <path> | Custom output path | | --no-validate | Skip pre-flight validation |


Pre-flight Validation

By default, all export commands run validation before generating output. This ensures your screenplay is error-free before export.

To skip validation:

wtfb export-pdf --no-validate

Configuration

The CLI respects project-level configuration files:

| File | Purpose | |------|---------| | cspell.json | Spell check configuration | | .cspell/project-words.txt | Custom dictionary | | .markdownlint-cli2.yaml | Markdown lint rules |


Output Directories

By default, exports are saved to:

exports/
├── pdf/     # PDF files
├── fdx/     # Final Draft XML
└── html/    # HTML previews

Requirements

  • Node.js 18+
  • For PDF export: afterwriting (installed automatically)

Related


License

MIT License - see LICENSE for details.