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

@reactive-forge/codegen

v1.0.0

Published

Code generation part of the Reactive Forge.

Downloads

64

Readme

@reactive-forge/codegen

Code generation part of the Reactive Forge.

This package provides function that can be used to generate metadata for react components and cli tool that wraps around this function and also provides command for generating config file.

Generating config

To generate config, run

npx forge init

and follow instructions from console. It will create forge.config.ts file in your current working directory.

Generating component metadata

First, you need to create config file. It can be either forge.config.ts, forge.config.js, forgerc.ts or forgerc.js. Default exported object must be assignable to ForgeConfig from @reactive-forge/codegen package.

Once you create it, you can run

npx forge codegen

or simply

npx forge

to generate argument information for your components. Note, that generated files will use types from @reactive-forge/shared package, and you will need to add it as your dependency when shipping your library to end-users.

Config

Available options:

| Field | Type | Default | Description | |--------------------|------------|----------------------------------------------------------|---------------------------------------------------------------------------------------------------------| | debug | boolean | false | enables debug output to the console | | silent | boolean | false | disables console output except for errors | | outDir | string | "reactive-forge" | directory to put output files in | | rootDir | string | "." | path to the root of the project | | baseDir | string | "src" | path to the roof of the componentsfile paths in the generated output will be relative to this path | | componentRoots | string[] | [baseDir] | root directories to start the search for components | | pathPrefix | string | "@/" | prefix of the file paths in the generated output | | tsConfigFilePath | string | path.resolve(rootDir, "./tsconfig.json") | location of tsconfig.json of the project | | typescriptLibPath | string | path.resolve(rootDir, "./node_modules/typescript/lib") | path to the typescript lib folderimportant when using workspaces | | reactTypesFilePath | string | | path to the index.d.ts of type for reactimportant when using workspaces |