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

@ifc-lite/codegen

v1.15.3

Published

TypeScript code generator from IFC EXPRESS schemas

Readme

@ifc-lite/codegen

TypeScript code generator for IFC EXPRESS schemas. Parses official .exp schema files from buildingSMART and emits typed TypeScript: 1000+ entity interfaces with full inheritance, schema metadata for runtime introspection, and exhaustive enum unions.

This is a build-time tool — you don't depend on it at runtime. The generated output ships with @ifc-lite/parser.

Installation

npm install --save-dev @ifc-lite/codegen

Generate from the official IFC schema

# IFC4 (776 entities)
npx ifc-lite-codegen ./schemas/IFC4.exp --out ./src/generated

# IFC4X3 (876 entities, includes infrastructure: roads, bridges, alignments)
npx ifc-lite-codegen ./schemas/IFC4X3.exp --out ./src/generated

Generated files (one per output directory):

src/generated/
├── entities.ts          ← TypeScript interfaces for every entity
├── schema-registry.ts   ← runtime metadata (parent, attributes, ...)
├── types.ts             ← enum unions and SELECT types
└── index.ts             ← barrel export

Programmatic usage

import { parseExpressSchema, generateTypeScript } from '@ifc-lite/codegen';
import { writeFile } from 'node:fs/promises';

const schema = parseExpressSchema('./schemas/IFC4.exp');

console.log(`Parsed ${schema.entities.length} entities, ${schema.types.length} types`);

const generated = generateTypeScript(schema, {
  inheritanceChain: true,
  emitEnums: true,
});

await writeFile('./src/generated/entities.ts', generated.entities);
await writeFile('./src/generated/schema-registry.ts', generated.schemaRegistry);

What you get

For an EXPRESS entity like:

ENTITY IfcWall
  SUBTYPE OF (IfcBuildingElement);
  PredefinedType : OPTIONAL IfcWallTypeEnum;
END_ENTITY;

You get a TypeScript interface with full inheritance:

export interface IfcWall extends IfcBuildingElement {
  PredefinedType?: IfcWallTypeEnum;
}

Plus runtime metadata for the same entity:

SCHEMA_REGISTRY.IfcWall = {
  parent: 'IfcBuildingElement',
  inheritanceChain: ['IfcRoot', 'IfcObjectDefinition', /* ... */, 'IfcWall'],
  attributes: [
    { name: 'PredefinedType', type: 'IfcWallTypeEnum', optional: true },
  ],
  allAttributes: [/* every inherited attribute, in inheritance order */],
};

Why generate vs. hand-write

  • Coverage: 776 IFC4 entities and 876 IFC4X3 entities — manual implementation gets ~7% there.
  • Updates: when buildingSMART releases a new schema, regenerate; no manual edits.
  • Consistency: every entity follows the same shape. Types, names, optional-ness all match the spec exactly.
  • Type safety: TypeScript catches schema-violating attribute access at compile time.

API

See the API Reference.

License

MPL-2.0