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

@croquet/virtual-dom

v1.0.9

Published

# Introduction

Downloads

15

Readme

Croquet Virtual DOM Framework

Introduction

Please refer to the document and the source code for general information on the Croquet Virtual DOM Framework.

A released version of Croquet (later than 1.0.4 release) is used to run Virtual DOM applications.

You can simply include

<script src="https://unpkg.com/@croquet/[email protected]"></script>

<script type="module">
   import {makeMain, Library} from "https://unpkg.com/@croquet/[email protected]";
   ...
</script>

in your HTML file to load the Croquet library and the Virtual DOM framework. In general, you don't need to use JS packager or bundlers.

Deployment

When you prefer to create a deployment where a fewer files are loaded, you can roll up your Virtual DOM expander files into one. However, for expanders to function properly, the class and method names need to be preserved, therefore the way they are bundled needs some care. The following describes the suggested way to bundle your expander files.

  1. add devDependencies to your package.json, (or run npm install for those packages):
"devDependencies": {
    "@babel/core": "^7.14.6",
    "rollup": "^2.52.7",
    "rollup-plugin-babel": "^4.4.0",
    "rollup-plugin-terser": "^7.0.2"
}
  1. create a rollup.config.js file:
import { terser } from 'rollup-plugin-terser';

const config = {
    plugins: [
        terser({
            mangle: {
                module: true,
            },
            keep_classnames: true,
            keep_fnames: true,
        }),
    ]
};

export default config;
  1. create the entry point file (say, app.js) of all your expander files:
export {a} from "./a.js";
export {b} from "./b.js";
...

where a.js, b.js, etc. are the Virtual DOM expander files.

You can then create a single file (dist/app.js) that includes all expander files:

npx rollup app.js --config rollup.config.js --file dist/app.js --format es

The HTML or other files that loads app.js does not have to be changed.