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

@feelpp/asciidoctor-extensions

v1.0.0-rc.17

Published

Asciidoctor Extensions by Feel++.

Downloads

278

Readme

:feelpp: Feel++

Asciidoctor Extensions by {feelpp}

A set of Asciidoctor extensions used by https://github.com/feelpp/feelpp[> {feelpp}]. There are not tied to {feelpp} and could be useful to other software.

== Executable Python blocks

Python source blocks with the dynamic option are executed only when the document declares :dynamic-blocks:. Blocks on one page share one IPython session and run in document order.

The execution contract can be configured with document attributes:

[cols="2,2,3",options="header"] |=== |Attribute |Default |Meaning |dynamic-python-interpreter |python3 |Interpreter executable used without a shell |dynamic-blocks-strict |false |Fail the document when any dynamic block fails |dynamic-blocks-timeout-seconds |60 |Maximum duration for all dynamic blocks on one page; maximum 600 |dynamic-blocks-max-output-bytes |5242880 |Aggregate captured stdout and stderr limit; maximum 104857600 |dynamic-python-isolate-user-site |false |Use an isolated home and disable Python user-site packages |===

Required blocks can also declare fail-on-error individually. Matplotlib blocks require a non-empty figure-alt attribute.

The child process receives an allowlisted environment. Arbitrary tokens and credentials are not inherited. Temporary paths are redirected to a workspace that is removed after success or failure. When dynamic-python-isolate-user-site is enabled, the home, cache, IPython, and Matplotlib paths are isolated as well, and imports cannot fall back to packages from the user's home directory. Enable it in locked virtual environments; the compatibility default retains user package and cache discovery for existing installations.

[IMPORTANT]

This feature executes trusted documentation code; it is not an operating-system sandbox. Run it in a job with read-only repository permissions, no publishing credentials, no private content checkout, and appropriate container or runner isolation.