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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@milaboratories/pframes-rs-node

v1.0.109

Published

PFrames - Node.js Native Addon

Downloads

2,162

Readme

PFrames Node.js native addon

Usage

[!TIP] Install using pnpm install @milaboratories/pframes-rs-node command. Check tests for usage examples.

Build instructions

Build steps

pnpm run build

Artifacts

NodeJS Native Addon is places in dist folder. Use pnpm run pack to prepare an archive (last output line is its path) and upload it to AWS S3.

Export wrapper is placed in export_dist folder. Use pnpm publish to publish NodeJS package.

Debugging

Prerequisites

Debugging is only supported using VSCode with the following extencions installed (check @recommended section in VScode for more suggestions):

Launching debug session

  1. Clone and build the latest platforma-desktop-v2 (git clean -dffx && npm i && npm run build)
  2. Set the correct RELATIVE path to platforma-desktop-v2 in .vscode/settings.json variable platformaDesktopPath (default is ../platforma-desktop-v2)
  3. Build this package by following the build steps from above (for faster build use pnpm run dev-build)
  4. Use VSCode launch configuration for your platform to start debug session (VSCode debugging guide)

Performance profiling

  1. Clone and build the latest platforma-desktop-v2
  2. Set the correct RELATIVE path to platforma-desktop-v2 in .vscode/settings.json variable platformaDesktopPath
  3. Build this package by following the build steps from above
  4. Launch VSCode task (Cmd+Shift+P -> Tasks: Run Task -> Perf-profile platforma-desktop) for profiling
  5. Execute the test scenario and quite platforma-desktop
  6. Firefox profiler with recorded performance profile would automatically open in you browser of choice (Warning! Firefox profiler does not work in Safari and with AdBlock enabled)

Dump pframes requests

  1. Run platforma-desktop-v2 with MI_DUMP_PFRAMES_RS=/absolute/path/to/dump/requests npm run dev
  2. Archive the /absolute/path/to/dump/requests folder and pass to the developer