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 🙏

© 2024 – Pkg Stats / Ryan Hefner

module-exports

v2.2.1

Published

Get the exports of a module

Downloads

144

Readme

module-exports

Build Coverage Downloads

🐉 Note: this is new software doing complex things that hasn’t been used much. Here be dragons!

Get the exports of a module.

Contents

What is this?

This package finds out what is exposed from a module.

When should I use this?

You can use this to programatically figure out what can be used from a module. Primarily, so that you can then generate docs.

Install

This package is ESM only. In Node.js (version 18+), install with npm:

npm install module-exports

Use

import {toMarkdown} from 'mdast-util-to-markdown'
import {createFinder, defaultFormat} from 'module-exports'

const finder = createFinder()
const result = await finder(new URL('index.js', import.meta.url))

const tree = await defaultFormat(result.symbols)

console.log(toMarkdown(tree))

Yields:

### `Name`

Name fields.

###### Fields

* `name` (`Identifier | NumericLiteral | StringLiteral`)
  — name node
* `nameDisplay` (`string`)
  — serialized symbol name to sort on
* `nameDisplayPrefix` (`string`)
  — prefix to display before name
* `nameDisplaySuffix` (`string`)
  — suffix to display after name

<!-- … -->

### `defaultFormat(symbols)`

Format symbols.

###### Parameters

* `symbols` (`ReadonlyArray<Symbol>`)
  — list of symbols

###### Returns

Promise to an mdast tree of formatted symbols (`Promise<Root>`).

API

This package exports the identifiers createFinder and defaultFormat. It exports the TypeScript types Name, Result, Symbol, and Value. There is no default export.

Name

Name fields.

Fields
  • name (Identifier | NumericLiteral | StringLiteral) — name node
  • nameDisplay (string) — serialized symbol name to sort on
  • nameDisplayPrefix (string) — prefix to display before name
  • nameDisplaySuffix (string) — suffix to display after name

Result

Result.

Fields
  • messages (Array<VFileMessage>) — messages
  • symbols (Array<Symbol>) — symbols

Symbol

Value with name.

Extends
  • Name
  • Value

Value

Value without name.

Fields
  • description (Root | undefined) — symbol description
  • heritage (Array<Value>) — things this inherits from
  • parameters (Array<Symbol>) — parameters
  • properties (Array<Symbol>) — properties
  • return (Value | undefined) — return value
  • typeExpression (Type) — type of value itself
  • typeExpressionDisplay (string) — seralized type

createFinder()

Create a finder.

Parameters

There are no parameters.

Returns

Finder ((url: Readonly<URL>) => Promise<Result>).

defaultFormat(symbols)

Format symbols.

Parameters
  • symbols (ReadonlyArray<Symbol>) — list of symbols
Returns

Promise to an mdast tree of formatted symbols (Promise<Root>).

Compatibility

This projects is compatible with maintained versions of Node.js.

When we cut a new major release, we drop support for unmaintained versions of Node. This means we try to keep the current release line, module-exports@2, compatible with Node.js 18.

Version

module-exports does not strictly follow SemVer yet while being super new.

Thanks

Special thanks go out to:

Security

This package is safe.

Contribute

Yes please! See How to Contribute to Open Source.

License

MIT © Titus Wormer