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

local-links

v1.4.1

Published

Determine cross-browser if an event or anchor element should be handled locally.

Downloads

40,111

Readme

local-links

Determine cross-browser if an event or anchor element should be handled locally.

NPM Build Status Sauce Test Status

Install

npm install local-links --save

Why?

Browsers have quirks. Knowing if a link is local should be easy, since we just want to know if the hosts are the same. But this can be difficult because of the aforementioned browser quirks. A few of them:

  • IE9 will add :80 to the host of an anchor, but not the window
  • IE9 wont put a leading slash on the pathname of an anchor, but will on the window
  • Chrome 36 will report anchor.hash as '' if it has href="#"
  • More? Please report test cases!

Because of that and a few other things I was doing all the time, such as finding the closest anchor to an element based on an event object, I decided it would be a good module (that at least I would use all the time).

Usage

<a href='/page2' id="local">Local</a>
<a href='#hash' id="hash">Local</a>
<a href='http://google.com' id="google">Google</a>
var local = require('local-links');

// `pathname()` will return the pathname as a string
// if the link is local, otherwise it will return null
local.pathname(document.getElementById('local')) // '/page2'
local.pathname(document.getElementById('hash')) // null
local.pathname(document.getElementById('google')) // null

// `hash()` will return the hash as a string
// if the hash is to this page, otherwise it will return null
local.hash(document.getElementById('local')) // null
local.hash(document.getElementById('hash')) // '#hash'
local.hash(document.getElementById('google')) // null

API

Methods

getLocalPathname(Event or HTMLElement [, HTMLElement])

Returns the pathname if it is a non-hash local link, or null if it is not. Always includes the leading /.

Alias: pathname

getLocalHash(Event or HTMLElement [, HTMLElement])

Returns the hash if it is an in-page hash link, or null if it is not. Always includes the leading #.

Alias: hash

isActive(Event or HTMLElement [, String comparePath])

Returns true/false depending on if the anchor pathname is equal to the comparePath (which defaults to window.location.pathname). Calls pathname() internally.

Alias: active

isLocal(event, anchor, [, Boolean lookForHash])

Returns the pathname (or hash if lookForHash is true) for local links, or null if it is not. This is used by pathname() and hash() under the hood. The main difference here is that you need to specify the event and anchor yourself, and the anchor wont be looked up from event.target like it would from the other methods.

Supply either Event or HTMLElement

The above methods will accept an Event object, like the one you get from click event handlers, or any HTMLElement. You can also supply an Event object and a different HTMLElement as the second parameter and it will take precedence.

If only an Event object is supplied, the HTMLElement will be found from Event.target.

Nested HTML Elements

In the case that any HTMLElement your provide is not an anchor element, the module will look up parentNodes until an anchor is found.

Events

If an Event object is supplied, all methods will return null if any of the following are true altKey, ctrlKey, metaKey, shiftKey. This is because you almost always want to treat modified click events as external page clicks.

target="_blank"

If the anchor has target="_blank" it will return null for both the pathname() and hash() methods.

Hash links

Using the pathname method will return null for hash links that do not point to a different page. To get the hash for one of these links use the hash() method.

Tests

Run npm start and open http://localhost:3000 to run the tests in your browser.

It is also a good idea to run sudo npm run start-80 (requires admin) which will run the tests on http://localhost because there can be unexpected behavior when the host has no port in IE9 and IE10.

To run the tests in the cli, just run npm test.

License

MIT