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

@bildit-platform/engine

v0.1.7

Published

BILDIT Render Engine

Readme

@bildit-platform/engine

@bildit-platform/engine is a dynamic module engine that allows you to evaluate and interpret module code on the fly in a controlled environment. It automatically registers a global module creator and injects specific dependencies into dynamically evaluated modules.

Features

  • Global Module Registration: Automatically registers a global define function (and sets React) so that evaluated modules can access controlled dependencies.
  • Dynamic Module Interpretation: Provides a safe way to evaluate module code strings and retrieve specific exports.
  • Dependency Injection: Uses a dependency injection mechanism to supply controlled dependencies (such as React and jsx-runtime) to your module factory functions.

Installation

Install via npm:

npm install @bildit-platform/engine

Or via yarn:

yarn add @bildit-platform/engine

Usage

When you import @bildit-platform/engine, it automatically registers a global module creator on globalThis (or window in browsers) and sets up the React dependency. The library provides two main functions: interpretModuleString and createModuleWithDependencies.

Global Registration & Module Interpretation

The library registers a global define function that you can use for dynamic module creation. The helper function interpretModuleString evaluates a module code string and returns the desired export.

Example

import {interpretModuleString} from '@bildit-platform/engine/react';

const moduleCode = `
  ({
    default: function hello() { return 'Hello, world!'; },
    extra: 'Additional export'
  })
`;

const helloFunction = interpretModuleString(moduleCode); // Defaults to 'default'
console.log(helloFunction()); // Outputs: Hello, world!

const extraExport = interpretModuleString(moduleCode, 'extra');
console.log(extraExport); // Outputs: Additional export

Dependency Injection with createModuleWithDependencies

import {createModuleWithDependencies} from '@bildit-platform/engine/react';

const moduleExports = createModuleWithDependencies(
  ['exports', 'react', 'react/jsx-runtime'],
  (exports, React, jsxRuntime) => {
    // Example: Attach a React component to the module exports.
    exports.MyComponent = () => React.createElement('div', null, 'Hello from MyComponent');
  }
);

console.log(moduleExports.MyComponent()); // Renders your component

API Reference

interpretModuleString

Interprets JavaScript module code from a string and returns the specified export.

Signature:

function interpretModuleString<T = unknown>(
  moduleCode: string, 
  exportName?: string, 
  extraDependenciesConfig: Record<string, ExtraDependencyConfig>
): T | null;

Parameters:

  • moduleCode: The JavaScript module code as a string.
  • exportName (optional): The name of the export to retrieve. Defaults to 'default'.
  • extraDependenciesConfig (optional): Additional customer-specific dependencies.

Returns:

  • The specified export from the module code, or null if not found.

createModuleWithDependencies

Creates a module context with controlled dependencies.

Signature:

function createModuleWithDependencies<T extends Record<string, unknown>>(
  dependencies: string[],
  moduleFactory: (...args: unknown[]) => void,
  extraDependenciesConfig: Record<string, ExtraDependencyConfig>
): T;

Parameters:

  • dependencies: An array of dependency names required by the module.
  • moduleFactory: A factory function that receives the resolved dependencies as arguments and populates the module’s exports.
  • extraDependenciesConfig (optional): Extra dependencies configuration to set global name and module.

Returns:

  • An object containing the module exports.

Types

export type ExtraDependencyConfig = {
  module: any;
  globalName?: string;
};