npmpackage.info

Gathering detailed insights and metrics for koa2-history-api-callback

koa2-history-api-callback

base 'connect-history-api-fallback'

0.0.2

MIT

JavaScript

1,055 3

Installations

npm install koa2-history-api-callback

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

7.6.0

NPM Version

4.1.2 Score

Supply Chain

Quality

75.1

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

1

Total

3

Closed

2

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View all 2 contributors

Languages

JavaScript

JavaScript (100%)

Developer

luzuoquan

Download Statistics

Total Downloads

1,055

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

16 Stars

19 Commits

4 Forks

2 Watching

1 Branches

2 Contributors

Maintainers

Package Meta Information

Latest Version

0.0.2

Package Id

koa2-history-api-callback@0.0.2

Size

2.25 kB

NPM Version

4.1.2

Node Version

7.6.0

Total Downloads

Cumulative downloads

Total Downloads

1,055

Last day

Compared to previous day

Last week

400%

Compared to previous week

Last month

-50%

Compared to previous month

Last year

-11.8%

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

url

Versions

koa2-history-api-callback

base 'connect-history-api-fallback' for SPA

Reason

Koa v2.x don't use yield*, so'koa-connect-history-api-fallback' can't adapter for Koa v2.x .

Adapter for 'connect-history-api-fallback' for use with Koa ^2.0.0.

Solution

1.use 'koa2-history-api-callback' 2.use 'koa-convert' convert old middleware ...

Installation

$ npm install --save 'koa2-history-api-callback'

Example

const Koa = require('koa')

const historyFallback = require('koa2-history-api-callback')

app.use(historyFallback())

app.use('other middleware')

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.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

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

0

Maintained

Determines if the project is "actively maintained".

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.

Score

3

/10

Last Scanned on 2024-12-16

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