npmpackage.info

Gathering detailed insights and metrics for manup

Other packages similar to manup

ionic-manup

2.0.0

Mandatory Update for Ionic 2+ apps

@kurkle/color

0.3.4

css color parsing, manupulation and conversion

ionic-manup-no-cache

1.0.2

Mandatory Update for Ionic 5 app, no save in cache .JSON

igtb-ionic-manup

1.0.0

Images package for npm

Gathering detailed insights and metrics for manup

manup

1.0.1

Apache-2.0

JavaScript

586.00 B

6,564 3

Installations

npm install manup

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

6.5.0

NPM Version

3.10.6 Score

Supply Chain

86.1

Quality

75.1

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

0

Closed

0

Issues

Open

0

Total

0

Closed

0

Releases

Unable to fetch releases

Contributors

Unable to fetch Contributors

View all 1 contributors

Languages

JavaScript

JavaScript (100%)

Developer

ahoereth

Download Statistics

Total Downloads

6,564

Last Day

Last Week

Last Month

Last Year

428

GitHub Statistics

7 Commits

3 Watching

1 Branches

1 Contributors

Bundle Size

2.14 kB

Minified

586.00 B

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

1.0.1

Package Id

manup@1.0.1

Size

5.89 kB

NPM Version

3.10.6

Node Version

6.5.0

Total Downloads

Cumulative downloads

Total Downloads

6,564

Last day

Compared to previous day

Last week

-20%

Compared to previous week

Last month

400%

Compared to previous month

Last year

-77.4%

428

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

No dependencies detected.

Versions

ManUp.js

Provides the function manup() which given a Web App Manifest object generates according meta and link tags for older browsers. Output is an array of arrays of which the first value is the tag (meta or link) and the second value is the object of attribute/value pairs.

Install

npm i manup

Usage

import manup from 'manup';

const manifest = JSON.parse(fs.readFileSync('./manifest.json', 'utf8'));
const headElements = manup(manifest);

Example manifest.json:

{
  "short_name": "ManUp.js",
  "icons": [
    {
      "src": "/icon-192.png",
      "sizes": "192x192",
      "type": "image/png"
    }
  ],
  "start_url": "/",
  "display": "standalone",
  "theme_color": "#f44336"
}

Example output headElements array:

[
  [ 'meta', { name: 'theme-color', content: '#f44336' } ],
  [ 'meta', { name: 'mobile-web-app-capable', content: 'yes' } ],
  [ 'meta', { name: 'apple-mobile-web-app-capable', content: 'yes' } ],
  [ 'meta', { name: 'apple-mobile-web-app-title', content: 'ManUp.js' } ],
  [ 'meta', { name: 'application-name', content: 'ManUp.js' } ],
  [ 'meta', { name: 'msapplication-navbutton-color', content: '#f44336' } ],
  [ 'link', { rel: 'icon', sizes: '192x192', href: '/icon-192.png' } ]
]

Browsers will choose whether to use the manifest.json or the tags.

Usage with React

const Html = ({ headElements }) => (
  <html lang='en-EN'>
    <head>
      <title>ManUp.js</title>
      <link rel='manifest' href='/manifet.json' />
      {headElements.map(([tag, props], idx) =>
        React.createElement(tag, { ...props, key: idx })
      )}
    </head>
    <body>
      <div id='app' />
    </body>
  </html>
);

Props

The foundation for this comes from https://github.com/boyofgreen/ManUp.js -- thanks! The code was simplified and rewritten as a node module and some more supported tags added.

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

SAST

Determines if the project uses static code analysis.

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.

Score

3

/10

Last Scanned on 2025-02-03

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