Skip to content

Publishing freedom.js modules

soycode edited this page Oct 21, 2015 · 3 revisions

So you've worked hard and made a freedom.js-powered module, enabling some nifty functionality for users or perhaps supporting some larger project. What's next? How do you share it with the world? There's no universal answer, but here are some typical options:

  • If your work is open source, release the source in a repository somewhere (here on GitHub, or some competitor, or maybe self-host)
  • If you've made a module meant to help other developers, then releasing a built version on npmjs is probably a good idea
  • If you've made something meant to be run by users in a browser as a webpage, then (assuming you're a fairly pure freedom.js/clientside JavaScript app) all you really need is a static host, of which there are many (these are all somewhat developer-oriented, but you can also use just about any traditional webhost, server, VPS, or platform like AWS, or even file hosting services like Dropbox)
  • If you've made something meant to by run by users as a browser addon/extension (i.e. freedom-for-firefox or freedom-for-chrome) then you should read through the browser vendors documentation to figure out getting your addon officially signed and included in whatever store/marketplace they have
  • If you've made something that uses freedom.js on the server (i.e. freedom-for-node) then you need some server with node.js to run it (you can likely figure this out from having set up your development environment)

Another thing you can do is integrate other typical developer tools from the JavaScript ecosystem (for building, testing, etc.). We use some of these in freedom.js, see the various badges and links in the README.md files of our repositories to get an idea.