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

@gigwalk/navigator-js

v1.0.5

Published

A tiny yet powerful library to deal with navigation and flow in your JavaScript projects.

Downloads

21

Readme

navigator.js Build Status

NavigatorJS is the ultimate solution to show/hide your dom-elements based on a single state string. This library was created to take away your pains when it comes to navigating your (single page) application between different views or application states. It provides ways to deal with (asynchronous) transitions between states without bugging you with the tedious parts. To sum up of the library's features:

  • Total control over synchronous and asynchronous visual transitions
  • Just-in-Time initalization of view components
  • DebugConsole to show exactly which elements are uninitialized, hidden or visible
  • Support for dynamic range elements and lists, like gallery items
  • Nested states, move complete parts of you application and they still work
  • Flow control through state validation, both synchronous and asynchronous
  • Optional integration with Backbone
    And many more...

NavigatorJS is mostly ported from the popular AS3 library Navigator-as3, created by @epologee. Most work was done by Paul Tondeur, later joined by Michiel van der Ros. They are both members of the Bigger Boat freelance collective in Amsterdam.

Running the specs

Navigator.js was build with TDD. We created a test suite with Jasmine gem. Every commit and pull requests gets tested with Travis-ci.

You can run the test locally by installing Ruby 2.x.x. For more information on how to install Ruby check the Rbenv installation guide. To run the other commands, you will need the Bundler gem if you don't have it yet. (You may need to add 'sudo' in front of this command.)

$ gem install bundler

When you have Ruby and Bundler installed run this command to install all dependencies:

$ bundle install

To see the tests in a browser run this command:

$ bundle exec rake jasmine

Then open your browser with this url; http://localhost:8888/

Usage

Please refer to the examples, tests and Navigator-Injector-Backbone-Command-TodoMVC example for details of how this library can be used.

Writing full documentation of all its features is on the roadmap

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request from Github