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

mprint-xmlrpc

v1.0.1

Published

An edited, pure JavaScript XML-RPC client and server.

Downloads

3

Readme

mprint-xmlrpc

XMLRPC library for MPrint Server

This is based on the node-xmlrpc repository, which has a bug dealing with Float values, but is no longer maintained.

In essence, PaperCut's XMLRPC server uses Java and is very strictly-typed, so its methods expect, for example, a Double vs. an Int in some cases. This is an issue when we're trying to adjust a user's balance by an integer value, because JavaScript is not strictly typed -- all 'number' types are represented by floats but are displayed with or without a decimal point, based on if it's an integer or not. When the XMLRPC library tries to serialize the values into XML, it sees something like 10 and says "it's an integer", even though the Java server requires it to be a Double. To work around that, if you try to run parseFloat to force a decimal point, it returns a String value, so the library sends it as a String instead of a Double.

So! We need to throw a condition into the serializer to say, if it's a String value, but is actually representative of a number, send it as a Double.