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

node-firefox-marketplace

v0.0.3

Published

Communicate with the Firefox Marketplace API

Downloads

8

Readme

WIP node-firefox-marketplace

JavaScript library for communicating with the Firefox Marketplace.

This is a work in progress. The library currently only supports validating a manifest and uploading it to the Marketplace so you can continue the app submission process.

Install

npm install node-firefox-marketplace

Usage

var MarketplaceClient = require('node-firefox-marketplace');

var fxos = new MarketplaceClient(options);

where options is an object consisting of: consumerKey (String) consumerSecret (String) environment (String) can be either development or production. If left blank, it will default to 'development'

The consumerKey and consumerSecret properties should correspond to your Marketplace Developer API key pair.

For development, you can generate OAuth keys on the Beta Firefox Marketplace here.

To work with the production Firefox Marketplace, you can generate your API keys here.

Choose 'command line' for the client type when generating your key.

Validating a manifest file

fxos.validateManifest(manifestUrl).then(function(result) {
  console.log('Result: ', result);
});

manifestUrl is a hosted manifest.webapp URL. (i.e. http://brittanystoroz.github.io/its-five-o-clock-somewhere/manifest.webapp). The promise resolves with the response body object, which might look something like this:

{ id: '30d2555502e046b4a92b31e8dac233e2',
  processed: true,
  valid: true,
  validation: { 
    ending_tier: 2,
    success: false,
    warnings: 1,
    feature_profile: [],
    messages: [ [Object], [Object], [Object], [Object] ],
    metadata: {},
    manifest: false,
    errors: 0,
    notices: 0,
    feature_usage: {},
    permissions: []
  }
}

Assuming the manifest is valid, you can then use the id property to publish your application to the marketplace.

Validating a packaged application

fxos.validatePackage(packagePath).then(function(result) {
  console.log('Result: ', result);
});

packagePath is a path to a local webapp package (normally a zip file). The promise resolves with the same results as documented above in the validateManifest method.

Publishing an app

fxos.publish(validationId, format).then(function(result) {
  console.log('Result: ', result);
});

validationId is the id property from the object returned by the validateManifest or validatePackage method. The format is needed, if you are publishing a packaged app and has to hold the value "packaged", when publishing a validated manifest the value doesn't matter. The promise resolves with an application object, and you will see your newly created app under 'My Submissions' in the Marketplace Developer Hub.