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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fumadocs-python-autodoc

v0.0.3

Published

Python autodoc for FumaDocs

Downloads

19

Readme

Python autodoc for Fumadocs

See it in action here.

Features

  • Fully autogenerated API documentation for entire packages
  • Cross-references to itself and the sources specified in the config
  • Includes source code in the documentation
  • Generates a page for each module Easily add source code documentation to your Fumadocs documentation site (assumes you have Fumadocs already set up):
  • Custom source for fumadocs (includes structured data for search implementation)

Usage

  1. Export your source documentation to json. Assumes you have a python environment with fumadocs-autodoc and the package to document installed.
fumadocs-autodoc <pkg_name> --dir ./lib
  1. Add a config file fumapy.config.ts in the root of your project. Here you specify each package to document:
// fumapy.config.ts
import { Config } from "fumadocs-python-autodoc/source";

const config: Config = {
  shiki: {
    lang: "python",
    themes: {
      dark: "vitesse-dark",
      light: "vitesse-light",
    },
  },
  jsonPath: "lib",
  sources: {
    bamboost: {
      baseUrl: "autodoc",
      title: "API Reference",
      pkgName: "bamboost",
      sortClassMethods: true,
      gitUrl: "https://gitlab.com/cmbm-ethz/bamboost/-/blob/next/bamboost",
      excludeModules: ["bamboost._version"],
    },
  },
};

export default config;
  1. Add a source in lib:
// lib/autodocSources.ts
import config from "@/fumapy.config";
import { getSources } from "fumadocs-python-autodoc/source";
import {
  setShikiConfigContext,
  setSourcesContext,
} from "fumadocs-python-autodoc/components";

export const autodocSources = getSources(config);

setSourcesContext(autodocSources);
setShikiConfigContext(config.shiki);
  1. Add a dynamic route in app/(apidocs)/[...slug] which handles the autodoc for all specified packages:
// app/(apidocs)/[...slug]/layout.tsx
import { ReactNode } from "react";
import { AutoDocLayout } from "fumadocs-python-autodoc/components";
import { baseOptions } from "@/app/layout.config";
import { autodocSources } from "@/lib/autodocSources";
import config from "@/fumapy.config";

export default async function Layout({
  children,
  params,
}: {
  children: ReactNode;
  params: Promise<{ slug?: string[] }>;
}) {
  const { slug } = await params;

  const comp = (
    <AutoDocLayout
      sources={autodocSources}
      shikiConfig={config.shiki}
      slug={slug}
      {...baseOptions}
    >
      {children}
    </AutoDocLayout>
  );
  return comp;
}
// app/(apidocs)/[...slug]/page.tsx
import { autodocSources } from "@/lib/autodocSources";
import { makePage } from "fumadocs-python-autodoc/components";

const { Page, generateStaticParams, generateMetadata } =
  makePage(autodocSources);

export default Page;
export { generateStaticParams, generateMetadata };
  1. Add stylesheet:
// global.css
@import "fumadocs-python-autodoc/preset.css";
  1. Add links to your layout and homepage. That's it.

See the example app in this repo for a working example.

Disclaimer

  • Docstrings are rendered using a Markdown pipeline. Assumes your docstrings are in Markdown format.
  • In terms of functionality this does not compete with mature autodocumentation tools like Sphinx or MkDocs.
  • This is an early adaption of my own workflow for bamboost. Contributions are welcome.
  • I am inexperienced with web development and typescript. Please be kind.