
Security News
npm ‘is’ Package Hijacked in Expanding Supply Chain Attack
The ongoing npm phishing campaign escalates as attackers hijack the popular 'is' package, embedding malware in multiple versions.
@imjakechapman/use-nested-match
Advanced tools
Currently with React Router V6 (still in alpha), using `activeClassName` on a top level `<NavLink>` on works with exact match. This hook helps mitigate the issue until they rework the internal `useMatch` to work correctly against nested routes.
Currently with React Router V6 (still in alpha), using activeClassName
on a top level <NavLink>
on works with exact match.
This hook helps mitigate the issue until they rework the internal useMatch
to work correctly against nested routes.
Example: https://codesandbox.io/s/react-router-v6-utility-function-usenestedmatch-44q73
useNestedMatch(test: string, opts: { type: string; path: string })
There are 2 type
options available
They do exactly what they sound like they do. startsWith
checks if the path starts with the test string and endsWith
checks if the path name ends with the test string. If you don't pass a type param it will match against the entire path.
provide a path to check against, default is ''
. For now I just pass pathname
you can retrieve from react-router-dom's useLocation
hook.
npm install @imjakechapman/use-nested-match
or
yarn add @imjakechapman/use-nested-match
then
We have some some nested routers and a top level NavLink
we want to stay active. import useNestedMatch
and test against whatever your heart desires.
location.pathname '/account/921808/somenestedroute/edit'
import { useLocation } from 'react-router-dom'
import { useNestedMatch } from '@imjakechapman/use-nested-match'
const App = () => {
const { pathname } = useLocation()
// returns true
const accountLinkActive = useNestedMatch('account', {
type: 'startsWith',
path: pathname
})
// returns false
const settingsLinkActive = useNestedMatch('settings') // false
// returns true
const editLinkActive = useNestedMatch('edit', {
type: 'endsWith',
path: pathname
})
return (
<NavLink className={
classnames({ 'my-active-class': accountLinkActive })
}>
Account
</NavLink>
<NavLink className={
classnames({ 'my-active-class': settingsLinkActive })
}>
Settings
</NavLink>
<NavLink className={
classnames({ 'my-active-class': editLinkActive })
}>
Edit
</NavLink>
)
}
FAQs
Currently with React Router V6 (still in alpha), using `activeClassName` on a top level `<NavLink>` on works with exact match. This hook helps mitigate the issue until they rework the internal `useMatch` to work correctly against nested routes.
We found that @imjakechapman/use-nested-match demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
The ongoing npm phishing campaign escalates as attackers hijack the popular 'is' package, embedding malware in multiple versions.
Security News
A critical flaw in the popular npm form-data package could allow HTTP parameter pollution, affecting millions of projects until patched versions are adopted.
Security News
Bun 1.2.19 introduces isolated installs for smoother monorepo workflows, along with performance boosts, new tooling, and key compatibility fixes.