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

addressbar

v1.0.3

Published

Makes the addressbar of the browser work just like a normal input

Downloads

442

Readme

addressbar

Makes the addressbar of the browser work just like a normal input

NPM version Build status Commitizen friendly Semantic Release js-standard-style

What is this thing?

How would you handle URLs if the addressbar was just an input? An input you could listen to changes, preventDefault() on and manually set the value without any sideeffect? What if you could think about changing the url as an event in your app, which you reacted to, instead of letting a route library swallow your view layer and mess around with it in a strongly opinionated way? What if you could have the freedom to make the URL mean whatever you wanted? Not just changes in what views to display?

The library just exposes the addressbar. It is a single entity in your app where you can:

// At http://www.example.com

addressbar.value // "http://www.example.com"

// Change addressbar value does NOT trigger route change
addressbar.value = "http://wwww.example.com/test";

// You can force a replace of the url setting an object as value
addressbar.value = {
  value: "http://www.example.com/test",
  replace: true
};

// You have access to location properties
addressbar.origin // "http://www.example.com"
addressbar.port // ""
addressbar.protocol // "http:"
addressbar.hostname // "www.example.com"
addressbar.pathname // "/"
addressbar.hash // ""

// Prevent route changes on hyperlinks
addressbar.addEventListener('change', function (event) {
  event.preventDefault();
  event.target.value // The value of the addressbar
});

This is low level code, so there is no routing logic here. Please check out url-mapper which can be used to create routing logic.

Under the hood

Addressbar listens to popstate events and handles hyperlinks. It basically has logic to simulate how an input works, also handling a few edge cases.

Tests

Addressbar is running with selenium-driver and nodeunit to test live in Chrome. Requires selenium chrome driver to be installed and added to PATH.

Run tests:

  • npm install
  • npm start (fires up a python webservice)
  • npm test (Runs tests)