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

@sect/use-placeholder-path

v1.4.1

Published

A custom React hook to retrieve placeholder path in Next.js App Router.

Downloads

283

Readme

@sect/use-placeholder-path

Release codecov CodeQL npm version NPM

A custom React hook to retrieve placeholder paths in Next.js App Router.

Why Use This Hook?

Next.js 13+ App Router doesn't provide a built-in method to return the path of placeholder values, unlike router.pathname in Pages Router. This hook fills that gap, allowing you to get the placeholder path in the App Router, similar to how you would in the Pages Router.

Easing the Transition from Pages Router

For developers migrating from Pages Router to App Router, this hook can significantly reduce the pain points associated with the transition. It provides a familiar way to access placeholder paths, making it easier to port existing code and maintain consistency in your application's routing logic. By offering functionality similar to router.pathname, usePlaceholderPath helps bridge the gap between the two routing systems, allowing for a smoother migration process and reducing the need for extensive refactoring of route-dependent code.

Installation

npm install @sect/use-placeholder-path
# or
yarn add @sect/use-placeholder-path
# or
pnpm add @sect/use-placeholder-path

Usage

'use client';

import usePlaceholderPath from '@sect/use-placeholder-path';

const MyComponent = () => {
  const placeholderPath = usePlaceholderPath();
  
  return (
    <div>
      <p>Current placeholder path: {placeholderPath}</p>
    </div>
  );
}

export default MyComponent;

API

usePlaceholderPath(options?: UsePlaceholderPathOptions): string

interface UsePlaceholderPathOptions {
  optionalCatchAllSegments?: string;
}
  • optionalCatchAllSegments: (optional) The name of the optional catch-all segment. If provided, enables handling of top-level optional catch-all segments.

Examples

  1. Route: /users/123/posts/456
    • Result: /users/[userId]/posts/[postId]
  2. Catch-all Segments Route: /blog/2024/08/15
    • Result: /blog/[...slug]
  3. Optional Catch-all Segments Route: /shop/a/b/c
    • Result: /shop/[[...slug]]

[!NOTE] For Top-Level Optional Catch-all Segments, special handling may be required. See the "Known Issues" section for more details.

Notes

Known Issues

Detecting Top-Level Optional Catch-all Segments

Top-Level Optional Catch-all Segments are expected to return /folderName/[[...segmentName]], but currently /folderName is returned.

  • Expected: /shop/[[...slug]]
  • Actual: /shop

This is due to the technical limitations in detecting Top-Level Optional Catch-all Segments in the Next.js App Router.

To address this limitation, we've introduced an optional configuration:

const placeholderPath = usePlaceholderPath({
  optionalCatchAllSegments: 'slug'
});

Changelog

See CHANGELOG.