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

use-current-url

v1.1.0

Published

A React hook to get the current URL.

Downloads

16

Readme

use-current-url

npm version

A React hook to get the current URL.

Takes into account URL rewrites made by proxies, load balancers, etc. along the way (as long as these append special HTTP headers to the request).

Installation

yarn add use-current-url

Usage

In its most basic form the useCurrentUrl() hook will, on mount, return the current URL:

import { useCurrentUrl } from 'use-current-url';

useCurrentUrl();
// => http://example.com/page

If your application uses server-side rendering you can pass in an initial URL via the CurrentUrlProvider component. There are also onMount and onUnmount hooks that can be used to trigger an update of the current URL.

For example, in a Next.js application you might add something like this to your root _app.jsx file:

import { getCurrentUrl, CurrentUrlProvider } from 'use-current-url';

const App = ({
  children,
  initialUrl,
}) => (
  <CurrentUrlProvider
    initialUrl={initialUrl}
    onMount={(updateCurrentUrl) => { Router.events.on('routeChangeComplete', updateCurrentUrl); }}
    onUnmount={(updateCurrentUrl) => { Router.events.off('routeChangeComplete', updateCurrentUrl); }}
  >
    {children}
  </CurrentUrlProvider>
);

App.getInitialProps = ({ req }) => (
  initialUrl: getCurrentUrl(req),
);

export default App;

Options

The following options are available for the CurrentUrlProvider

initialUrl

Type: string
Default: undefined

The initial URL to use when server-side rendering a page.

onMount

Type: function
Default: undefined

A callback to fire when the hook is mounted. It will be called with an updateCurrentUrl function, which in turn updates the current URL.

onUnmount

Type: string
Default: undefined

A callback to fire when the hook is mounted. It will be called with the same updateCurrentUrl function that is passed to onMount.