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

root-domain-lite

v1.0.2

Published

get root domain in browser

Downloads

5

Readme

browser-root-domain

Get root domain in browser.

Install

npm install --save root-domain-lite
# or
yarn add root-domain-lite

Why

Some domain sufixies are like .net.cn, while some are like .cn .io. See Public Suffix List.

For now, we do not have any perfect idea to distinguish between such cases. Enumeration? Crazy!

Don't sigh, we still have two idea that would help us:

if you set document.domain to .net.cn on a page, you would get an error;

you will not succeed when setting cookie with a domain=.net.cn option.

With the former idea, we could set document.domain repeatedly until success. For example, first try document.domain = 'net.cn', then try document.domain = 'xyz.net.cn'... Done!

Wait! Should we restore document.domain? Definitely!

Try to run document.domain = origianl_domain.

Chrome, hmm, OK.

Firefox? Oops!

It seems that, once document.domain is set to a superior one in Firefox, you can never set it back. Bad news.

So we have to turn to the latter idea. Cookie is not as stricky as document.domain. Just take a look at the source code ~