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

@aeco-dev/bonsaiweb

v0.0.1

Published

Browser BIM host: IfcOpenShell, a WebGPU viewer, and an optional gui shell.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

myoualidmyoualid

Keywords

Readme

@aeco-dev/bonsaiweb

Browser BIM host. It loads an IFC model, draws it in a WebGPU viewer, and exposes operators for a shell or a headless page.

npm install @aeco-dev/bonsaiweb

That installs this package and the libraries it imports: @aeco-dev/gui, @aeco-dev/layout, ifcopenshell, and @ifcopenshell/wasm. A bundler and a browser import map use those same names.

Bundler

import { start } from "@aeco-dev/bonsaiweb";
import { defaultPaths } from "@aeco-dev/bonsaiweb/paths";
import "@aeco-dev/gui/gui.css";
import "@aeco-dev/layout/layout.css";

Headless, without the shell: import { start } from "@aeco-dev/bonsaiweb/headless".

Import map

A page without a bundler maps the same names onto jsDelivr. The versions match the package dependencies. The map has to be inline, because the convert worker copies it.

<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/gui.css">
<link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/layout.css">
<script type="importmap">
{
  "imports": {
    "@aeco-dev/bonsaiweb": "https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/dist/bonsai.js",
    "@aeco-dev/bonsaiweb/headless": "https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/dist/bonsai-headless.js",
    "@aeco-dev/bonsaiweb/paths": "https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/dist/paths.js",
    "@aeco-dev/gui": "https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/gui.js",
    "@aeco-dev/layout": "https://cdn.jsdelivr.net/npm/@aeco-dev/[email protected]/layout.js",
    "ifcopenshell": "https://cdn.jsdelivr.net/npm/[email protected]/dist/index.js",
    "ifcopenshell/geom": "https://cdn.jsdelivr.net/npm/[email protected]/dist/geom/index.js",
    "ifcopenshell/util": "https://cdn.jsdelivr.net/npm/[email protected]/dist/util/index.js",
    "@ifcopenshell/wasm": "https://cdn.jsdelivr.net/npm/@ifcopenshell/[email protected]/browser.js",
    "@ifcopenshell/wasm/api": "https://cdn.jsdelivr.net/npm/@ifcopenshell/[email protected]/wasm/ifcopenshell_api.mjs"
  }
}
</script>
<script type="module">
  import { start } from "@aeco-dev/bonsaiweb";
  import { defaultPaths } from "@aeco-dev/bonsaiweb/paths";
</script>

The example in app/ uses that map, except @aeco-dev/bonsaiweb points at ../dist/ so a local rebuild shows up before the next publish.

defaultPaths is only the viewer scripts, zstd, and the worker shim. Those are not import specifiers.

The shell also needs configuration.ui, configuration.app, and configuration.ribbon. The example is app/configuration/config.js.