Gathering detailed insights and metrics for nextjs-redirect
Gathering detailed insights and metrics for nextjs-redirect
HOC to redirect to any URL in NextJS both in client and server
Installations
npm install nextjs-redirectDeveloper Guide
BETA
Typescript
Yes
Module System
CommonJS
Node Version
14.19.2
NPM Version
6.14.17
Releases
Unable to fetch releases
Languages
3
JavaScript
TypeScript
HTML
JavaScript (53.13%)
TypeScript (38.26%)
HTML (8.61%)
Developer
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
146 Stars
130 Commits
10 Forks
1 Watchers
2 Branches
2 Contributors
Updated on Jul 01, 2025
Maintainers
1
Package Meta Information
Latest Version
6.0.1
Package Id
nextjs-redirect@6.0.1
Unpacked Size
14.80 kB
Size
5.10 kB
File Count
5
NPM Version
6.14.17
Node Version
14.19.2
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
nextjs-redirect
Redirect to any URL in NextJS both in client and server
Install
1npm install nextjs-redirect
Usage
Let's say you want to create a page /donate that redirects the user to paypal.me with a default value for the money. You create the page as you always do in NextJS (pages/donate.js) and then just use this component with the URL you want:
1// pages/donate.js 2import redirect from 'nextjs-redirect' 3export default redirect('https://paypal.me/pablopunk/5')
You can checkout this example live in pablopunk.com
Status code (301, 302...)
By default, it will send a 301 status code. This can be customized by an optional parameter:
1redirect('https://google.es', { statusCode: 302 })
Client side dynamic routes (as)
When redirecting on the client side, if the redirected page is dynamic (pages/user/[userId]/info.js), the following redirect will trigger a page refresh:
1redirect('/user/42/info')
In this case you can use the asUrl option to make a smooth transition between pages without any refresh:
1redirect('/user/[userId]/info', { asUrl: '/user/42/info' })
Static export
This package is compatible with next export since version 4.0.0. See PR #4 for more details.
Custom UI component (HOC)
In case the navigation is happening client-side, you can use this package as a HOC to provide your custom components/styles for the UI:
1import redirect from 'nextjs-redirect' 2 3const Redirect = redirect('https://github.com/pablopunk') 4 5export default () => ( 6 <Redirect> 7 <MyLayout>Redirecting to github!</MyLayout> 8 </Redirect> 9)
Redirect to URL from parameters
Let's say you have a single page called /redirect, and you wanna use it for all kinds of redirects:
/redirect?to=https://google.com/redirect?next=https://twitter.com/redirect?url=https://pablopunk.com
Pretty cool huh!? You can do this with nextjs-redirect by passing the name of the parameter you want on the url. For the examples above:
1// NOTE: These are 3 separate examples, you can only choose one name per page 2redirect('to', {params: true}) 3redirect('next', {params: true}) 4redirect('url', {params: true})
Related
Working with locales routes? Take a look at nextjs-redirect-locale.
Native redirects
There's now a native way of handling redirects on NextJS. You can read more about it here. It requires you to modify your next.config.js. Personally I still think nextjs-redirect is a more friendly way of doing it, and also more flexible. For example you can do dynamic redirects on the server, depeding on the request, which is useful when working with locales (checkout nextjs-redirect-locale) and other request-dependent redirects. It also allows you make client redirects with a custom layout.
License
MIT
Author
 |
|---|
| Pablo Varela |
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/12 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/cypress.yml:1
- Warn: no topLevel permission defined: .github/workflows/static-export.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/cypress.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/pablopunk/nextjs-redirect/cypress.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/cypress.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/pablopunk/nextjs-redirect/cypress.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/static-export.yml:10: update your workflow using https://app.stepsecurity.io/secureworkflow/pablopunk/nextjs-redirect/static-export.yml/master?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/static-export.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/pablopunk/nextjs-redirect/static-export.yml/master?enable=pin
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 2 third-party GitHubAction dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 18 are checked with a SAST tool
Reason
18 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-f82v-jwr5-mffw
- Warn: Project is vulnerable to: GHSA-c59h-r6p8-q9wc
- Warn: Project is vulnerable to: GHSA-g77x-44xx-532m
- Warn: Project is vulnerable to: GHSA-7gfc-8cq8-jh5f
- Warn: Project is vulnerable to: GHSA-qpjv-v59x-3qc4
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-p8p7-x288-28g6
- Warn: Project is vulnerable to: GHSA-wf5p-g6vw-rhxx
- Warn: Project is vulnerable to: GHSA-jr5f-v2jv-69x6
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
- Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
- Warn: Project is vulnerable to: GHSA-pfrx-2q88-qq97
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-72xf-g2v4-qvf3
Score
2.5
/10
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More