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

@ldcv/stormjs

v0.5.10

Published

StormLib for Javascript, powered by Emscripten

Downloads

17

Readme

StormJS

Join Community Version MIT License CI Test Coverage

StormJS is StormLib for Javascript, powered by Emscripten.

StormLib is copyright © Ladislav Zezula. It is licensed under the MIT license. See src/vendor/StormLib/LICENSE for more information.

Usage

To install StormJS:

npm install @ldcv/stormjs

To use StormJS in an ES2015 module environment:

import { FS, MPQ } from '@ldcv/stormjs';

// Mount the local filesystem path /home/stormjs/example as /stormjs
// This approach is suitable for cases where StormJS is running under Node
FS.mkdir('/stormjs');
FS.mount(FS.filesystems.NODEFS, { root: '/home/stormjs/example' }, '/stormjs');

const mpq = await MPQ.open('/stormjs/example.mpq', 'r');
const file = mpq.openFile('example.txt');
const data = file.read();

// Clean up
file.close();
mpq.close();

To use StormJS in browser:

const { MPQ } = require('@ldcv/stormjs');

// Fetch MPQ file from the server
const mpqBuffer = await fetch("path/to/your.mpq").then(res => res.arrayBuffer());

// Read uploaded MPQ file from file input
const fileReader = new FileReader();
const mpqBufferInput = await new Promise(resolve => {
    fileReader.onload = evt => resolve(evt.target.result);
    fileReader.readAsArrayBuffer( document.querySelector("input[type='file']").files[0] );
});

const mpq = await MPQ.fromArrayBuffer(mpqBuffer);
const file = mpq.openFile('example.txt');
const data = file.read();

// Clean up
file.close();
mpq.close();

Then pack the script using a packaging tool, such as Browserify:

browserify -o bundle.js your-script.js

Note that StormJS loads in production mode if process.env.NODE_ENV is set to production. In all other cases, StormJS loads in debug mode.

For production mode in browsers, you may exclude the debug library --exclude node_modules/@ldcv/stormjs/dist/stormlib.debug.js from the packaging tool to reduce bundled script size.

API Reference

Please refer to API.md.

Compatibility

StormJS is tested against Node 10, 12, and 14; also tested in Chrome 92.

Additionally, StormJS should work well in other browsers with support for WASM. Note that use in browsers will require configuring an Emscripten filesystem type appropriate for the browser.

Development

Development of StormJS requires git, CMake, and an Emscripten environment.

emsdk is the simplest way to get an Emscripten environment up and running.

StormJS is currently built using Emscripten 1.39.15.

After cloning the StormJS repo, ensure all submodules are also pulled down from remote by running:

git submodule update --init --recursive

To build StormJS after making changes locally, run:

npm run build

The test suites for StormJS can be run using:

npm run test