Simply extract documentation comments from a source file.
Uses babel (babylon) to extract JavaScript code comments from a JavaScript string or file.
Uses esprima to extract line and block comments from a string of JavaScript. Also optionally parses code context (the next line of code after a comment).
Extract code comments from string or from a glob of files using esprima.
Extract comments from source files of various languages
No description provided.
An evented streaming XML parser in JavaScript
A parser for the TypeScript doc comment syntax
Strip comments from JSON. Lets you use comments in your JSON files!
Additional ESLint rules for ESLint directive comments.
extracts CSS into separate files
Additional ESLint rules for ESLint directive comments.
Extract C style comments and extract context from source
A lightweight URI template matcher based on RFC 6570
Zero-runtime Stylesheets-in-TypeScript
A CSS Modules transform to extract local aliases for inline imports
Zero-runtime Stylesheets-in-TypeScript
unzip a zip file into a directory using 100% javascript
Babel plugin to extract translatable messages from source code into Lingui catalogs
Parse and stringify JSON with comments. It will retain comments even after saved!
Extract javascript comments on per character basis. Comment object compatible with `acorn-extract-comments` and Esprima format.
Discard comments in your CSS files with PostCSS.
Extract comments from Solidity code
Plate plugin for comments
Generate document when reading source code from annotated comment. It extracts the source code of the place written as YOME: and outputs it in Markdown format.
Chiridion generates documentation optimized for AI agents and LLMs working with Ruby codebases. It extracts documentation from YARD comments, merges RBS type signatures, and produces structured markdown suitable for context injection. Features: - YARD-based documentation extraction - RBS type signature integration (RBS is authoritative) - RSpec example extraction - Obsidian-compatible wikilinks for cross-references - Drift detection for CI/CD pipelines - toys/dx CLI task definitions
==== QDox - http://qdox.codehaus.org QDox is a high speed, small footprint parser for extracting class/interface/method definitions from Java source files complete with JavaDoc @tags. It is designed to be used by active code generators or documentation tools. QDox is a Java library. Therefore this RubyGem needs JRuby. ==== Quickstart Step 1: Load your Java sources. In JRuby (or +jirb+) write: require 'qdox' builder = QDox::JavaDocBuilder.new builder.add_source_tree(java.io.File.new(".") (Source: http://qdox.codehaus.org/usage.html) Step 2: Inspect the source model. src = builder.sources.first pkg = src.package puts pkg.name # e.g. "com.bla.foo" imports = src.imports # => e.g. ["java.util.List", "java.util.Set"] some_class = src.classes.first # => a QDox::Model::JavaClass # output the javadoc comment for the first method in some_class puts some_class.methods.first.comment (Source: http://qdox.codehaus.org/model.html) As you may have noticed, the Java packages used have been aliased to shorter Ruby Module names: The Java package com.thoughtworks.qdox is the Ruby module QDox etc. ==== In a Nutshell A custom built parser has been built using JFlex and BYacc/J. These have been chosen because of their proven performance and they require no external libraries at runtime. The parser skims the source files only looking for things of interest such as class/interface definitions, import statements, JavaDoc and member declarations. The parser ignores things such as actual method implementations to avoid overhead (while in method blocks, curly brace counting suffices). The end result of the parser is a very simple document model containing enough information to be useful. ==== License Apache License, Version 2.0 QDox was created by Joe Walnes, Aslak Hellesoy, Paul Hammant, Mike Williams, Mauro Talevi, Robert Scholte, and others. The RubyGem was created by Benjamin Bock.
No description provided.
No description provided.
No description provided.