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

freedom-for-firefox

v0.6.26

Published

Embracing a distributed web

Downloads

74

Readme

freedom-for-firefox

Build Status

A freedom.js distribution for inclusion in Firefox extensions.

Installation

The freedom-for-firefox npm package contains a generated javascript code module, freedom-for-firefox.jsm. This file can be included in your firefox addon to interact with freedom.

freedom-for-firefox.jsm can be placed anywhere in your extension file structure. In the case of jetpack addons, you will likely want to place it somewhere in the data dir. To include it in jetpack addon, use:

const {Cu} = require("chrome");
// Note: data.url is relative to your data directory
Cu.import(self.data.url("freedom-for-firefox.jsm"))

Or in classic firefox extensions use:

Components.utils.import("freedom-for-firefox.jsm");

This will define the function freedom in the current scope, which behaves the same way as freedom in any other context.

Testing

grunt test will build an extension with jasmine integration tests and run the tests in Firefox. You can extend this with your own tasks, by including this dependency in your own grunt project:

grunt.loadNpmTasks('freedom-for-firefox');

You would then configure the build-test-addon task with your own jasmine tests, similarly to how it is run by this project.

Some helpful flags you can add to the grunt test command:

  • --firefox-debugger - fire up a JavaScript console running in the test addon
  • --verbose -d - get extremely verbose (debug-level) output

If you want the browser to stay open after the test run (e.g. to investigate more in the debugger console) you can change stayOpen in tasks/build-test-addon.js to true. You can also directly run the addon by installing jpm (npm install jpm -g) and then entering the .build/ path and executing jpm run.

FAQ

  • Mac OS X firewalls have been known to block WebRTC when set to its strictest setting. Be sure to allow an exception for Firefox for integration tests to pass