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

@doenet/assignment-viewer

v0.1.0-alpha-16

Published

View assignments from questions written in DoenetML

Readme

Doenet assignment viewer

View assignments from questions written in DoenetML

Mixed DoenetML versions

Each document in an assignment carries its own DoenetML version, and every embedded viewer downloads and parses the multi-MB standalone bundle for its document's version — so an assignment mixing versions multiplies that cost by the number of distinct versions on the page.

The viewer does not normalize versions itself (that would change how the older documents behave). Instead, when an assignment mixes versions, it reports the condition to the containing page — a console warning alone would be invisible to the site's visitors — via the reportWarningsCallback prop, and the page decides how to display it:

<ActivityViewer
    source={source}
    reportWarningsCallback={(warnings) => {
        for (const warning of warnings) {
            if (warning.type === "mixedDoenetmlVersions") {
                showBanner(
                    `This assignment mixes DoenetML versions (${warning.versions.join(", ")}), ` +
                        "which slows loading. Consider updating its documents to one version.",
                );
            }
        }
    }}
/>

To consolidate, normalize the documents' version fields in the assignment source. Saved student state survives such a change: it is keyed on a source hash that deliberately ignores version.

Windowed mounting

Every item's viewer component is always mounted, but memory tracks what the student can see — the pagination window or viewport — instead of the assignment's length. The embedded viewers register with a page-wide windowed mounting policy (mountPolicy from @doenet/doenetml-iframe): items only boot their iframe (a multi-MB bundle parse plus a core worker) when near the viewport or within the pagination window, simultaneous boots are capped, and at most maxLiveViewers stay live — the rest are parked: their state is flushed, their iframe is replaced by a placeholder, and they are restored (student's typed work intact) when the student returns to them. In paginated mode the current page and its neighbors are kept live, so page flips within the window stay instant.

This is the default. Tune it with the mountPolicy prop (overrides for maxLiveViewers, visibleMargin, parkDelayMs, flushTimeoutMs, maxConcurrentBoots):

<ActivityViewer
    source={source}
    flags={{ allowSaveState: true }}
    mountPolicy={{ maxLiveViewers: 5 }}
/>

Parking requires a persistence path (flags.allowSaveState or flags.allowLocalState) so no student work can be lost; without one, viewers still mount lazily but stay live once booted.

To cut the per-document core cost further, useSharedCoreWorker serves all documents' cores from a shared worker pool instead of one dedicated ~100 MB worker per document (default off; see @doenet/doenetml-iframe).