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

franky

v1.0.28

Published

JavaScript's functional programming helper library.

Downloads

6

Readme

Build Status

Franky.js

JavaScript framework for everyday usage

Environments to use

Franky is isomorphic JavaScript library. It may be executed on server side with a help of any javascript engine or on client side in browser

Requirements to build Franky

You need to have the latest Node.js/npm and git 1.7 or later.

For Windows, you may download and install git and Node.js.

Mac OS users may install Homebrew. Once Homebrew is installed, run brew install git to install git, and brew install node to install Node.js.

Linux/BSD users may use appropriate package managers to install git and Node.js, or build from sources.

How to build Franky

Clone a copy of git repo by running:

git clone [email protected]:ikondrat/franky.git

Enter the franky directory and run the build script:

cd franky && npm run build

The built version of franky will be put in the lib/ subdirectory.

Modules

The default configuration file conf/default.js will be used due build process.

Mind what it is linked as src/franky.js.

You may have another list of modules to build. For what case change link src/franky.js to your modified configuration file and run npm run build

Running the Unit Tests

Start npm test to auto-build franky and run tests:

cd franky && npm test

Annotated source

You may see annotated source