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

next-query-utils

v1.4.3

Published

Provides functions to manipulate parsed url query object

Downloads

879

Readme

Next Query Utils

License: MIT

[!NOTE]

This lib no longer updates in npm. latest: npm version

Instead, use JSR where it's published as v2.x or later

This library provides utility functions to deal with Parsed Query Objects (especially of Next.js)

このライブラリには、Parsed Query Object (特に Next.js のもの)を取り扱うためのユーティリティ関数群が含まれます。

Links — リンク集

Install

// with npm
npm i next-query-utils

// with yarn
yarn add next-query-utils

Usages — 使い方

Getting single value — 単独の値を取得する

?id=aaa or ?id=aaa&id=other -> "aaa"


// before
const _id = router.query["id"]
const id = Array.isArray(id) ? id[0] : id

// after
const id = getSingleQueryParam(router.query, "id")

Removing some params — 値を取り除く

?start_on=2022-03-02&item_type=stationary&item_type=book -> ?start_on=2022-03-02&item_type=stationary

Before

// before
const removeQuery = (
  query: ParsedUrlQuery, 
  key: string,
  pred: string
) => {
  const value = query[key]

  // if empty, leave query as it is.
  if (!value) return query;
  if (Array.isArray(value)) {
    if(value.length === 0) return query;

    // if non-empty array of string
    return { ...acc, [key]: value.filter(s => s !== pred) };
  }

  // if single string (not empty)
  return { ...acc, [key]: (s !== value) ? value : [] };
}

After

// after
router.push(
  removeQueryParam({ 
    item_type: "book"
  })(router.query)
)

Keeping some params (or Next.js's dynamic routes) from being reset — (Next.js's の動的ルートや)パラメータを残して他を削除する

/[postId]?other=value&other2=value -> /[postId]


In pages with Next.js's dynamic routes, router.query include them (in this example, .postId). so they MUST be kept from resetting.

In this case, use resetQuery() with ignore option.


Next.js の動的ルートがあるページでは、それが router.query に含まれる。(この例では .postId) なので、それらは 削除してはいけない

このようなケースでは resetQuery()ignore オプションを使いましょう。


// before
router.push({ postId: router.query["postId"] })

// after
router.push(resetQuery({ ignore: "postId" })(router.query))

Checking if query is empty ignoring some params (e.g. dynamic routes)— (動的ルートのような)パラメータ幾つかを無視して、クエリが空であるか確かめる

  • True if /items/[postId]
  • False if /items/[postId]?param1=aa

Likewise, you need to ignore dynamic routes in order to check if the query is empty.

In this case, use isQueryEmpty() with ignore option.


前の例と同じように、クエリが空であるか確かめるためには、 動的ルート を無視する必要があります。

このようなケースでは、isQueryEmpty()ignore オプションを使いましょう。


isQueryEmpty(router.query, { ignore: "postId" })

License

This library is licensed under the terms of MIT License