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

mozilla-get-url

v0.4.3

Published

Utility to get the url of a particular version/release of a mozilla product (like firefox/b2g)

Downloads

17

Readme

mozilla-get-url

Find the url where a given mozilla product lives for all kinds of branches / releases / pre-releases.

Inspired by firefox-get which I initially contributed to for the b2g-support... The primary difference is mozilla-get-url is designed to handle most mozilla products up front and uses ftp rather then html scraping.

Usage

var locate = require('mozilla-get-url');

var options = {
  /**
    - optional
    - default: release
    - examples: ['release', 'prerelease', 'tinderbox', 'try']
  
  Channels determine how builds are fetched and map to lib/channels/$CHANNEL.
  Not all options are available across all channels
  */
  channel: null,

  /*
    - required
    - examples: 'win32', 'mac', 'linux-i686', 'linux-x86_64'
  */
  os: 'mac',

  /*
    - optional
    - default: 'latest'
    - examples (release channel): '17.0', '3.6', 'latest', 'beta'
    - examples (prerelease channel): 'aurora', 'nightly', 'mozilla-central'
    - examples (tinderbox channel): 'mozilla-central', 'mozilla-inbound'
    - examples (try channel): '[email protected]'

  What type of available branches vary on the channel.
  */
  branch: '17.0',
  /*
    - optional
    - default: 'en-US'

  Only used in the "release" channel.
  List of languages: http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest/linux-x86_64/
  */
  language: 'en-US',

  /*
    - optional
    - default: 'firefox'
    - examples: 'firefox', 'b2g'
  
  Gecko product... Only tested with firefox and b2g-desktop (b2g)
  */
  product: 'firefox',

};

locate(options, function(err, url) {
  url; // => http url to the build
});

CLI Usage

# get latest firefox
mozilla-get-url --os mac

# get latest b2g-desktop from mozilla central
mozilla-get-url --channel tinderbox --os mac --branch mozilla-central --product b2g