Installations

npm install next-isomorphic-link

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

10.13.0

NPM Version

6.4.1 Score

27.1

Supply Chain

53.6

Quality

75.1

Maintenance

100

Vulnerability

92.3

License

Pull Requests

Open

3

Total

11

Closed

3

Merged

5

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

1

Unable to fetch Contributors

View all 1 contributors

Languages

1

JavaScript

JavaScript (100%)

Developer

alexbassy

Download Statistics

Total Downloads

2,300

Last Day

1

Last Week

6

Last Month

16

Last Year

155

GitHub Statistics

2 Stars

28 Commits

1 Watching

4 Branches

1 Contributors

Bundle Size

1.77 kB

Minified

894.00 B

Minified + Gzipped

Bundlephobia

Maintainers

1

Package Meta Information

Latest Version

0.2.5

Package Id

next-isomorphic-link@0.2.5

Unpacked Size

9.96 kB

Size

4.90 kB

File Count

5

NPM Version

6.4.1

Node Version

10.13.0

Total Downloads

Cumulative downloads

Total Downloads

2,300

Last day

0%

1

Compared to previous day

Last week

-33.3%

6

Compared to previous week

Last month

33.3%

16

Compared to previous month

Last year

-31.7%

155

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Peer Dependencies

2

next react

Dev Dependencies

5

@babel/cli @babel/core @babel/preset-env @babel/preset-react typescript

Versions

next-isomorphic-link

A tiny Next.js <Link/> wrapper that improves server-side rendered output with better keyboard navigation support

Usage

yarn add next-isomorphic-link

Replace import from of next/link with next-isomorphic-link:

1- import Link from 'next/link'
2+ import Link from 'next-isomorphic-link'

Why

The default <Link/> component usage looks like this (as of Next 9):

1<Link href='/puppies'>
2  <a>Puppies</a>
3</Link>

When you view the source, or disable JavaScript, the markup will look like this:

1<a>Puppies</a>

There are a few issues here:

<a> tags without href attributes are not tabbable (you can’t tab around the page)
When the page has’nt been rendered client side (e.g. JS disabled, slow network speed) the link will not be clickable
Once the bundle has been executed and the page is interactive, hitting Enter (or the spacebar if you have that option enabled) when focussed on the link will have no effect.

These are easy to fix:

Add the href attribute to the child <a> in the server-rendered markup (and remove it when mounted)
Add a tabIndex of 0 to the client-side rendered link to ensure tabbability (if that is a word)
Add an event handler for the Enter key

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/10

Last Scanned on 2025-01-27

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