npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

create-polyfill-service-url

v2.3.1

Published

Analyse your JavaScript file and generate a polyfill.io URL based on all the features that are being used from within the JavaScript file.

Downloads

9,098

Readme

Polyfill.io URL Builder

A Node.js command-line application for analysing your JavaScript file and generating a https://polyfill.io URL based on all the features that are being used from within the JavaScript file.

NPM version MIT licensed

> npx create-polyfill-service-url analyse --file bundle.js

Table Of Contents

Usage

CLI

This project requires Node.js 10.x and npm. You can run it with:

> npx create-polyfill-service-url analyse --file bundle.js [--cwd "/custom/pwd" --omit "Array.prototype.includes" --hostname "polyfill.io"]

You can pass multiple files as argument if you split your bundle files:

npx create-polyfill-service-url analyse --file app.js vendor.js

| Option | Description | Default | |-------------------------------|-------------------------------------------------------------------------------------------------------------|-----------------| | --file | The path to the JavaScript file(s) to analyse | | | --cwd | The current working directory | process.cwd() | | --omit | A list of features to omit. Example: Array.prototype.map | | | --hostname | The hostname of the polyfill service to use. | polyfill.io | | --use-compute-at-edge-backend | Defines the compute-at-edge-backend usage policy: yes or no. If empty the server will decide. | | | --flags | Configuration settings for every polyfill being requested. Possible values are always and gated or both | | | --unknown | Defines the policy for unsupported browsers: polyfill or ignore | polyfill |

JS API

const analyze = require('create-polyfill-service-url');

const result = await analyze({
  file: ['bundle.js'],
  cwd: '/foo/bar',                    // Defaults to process.cwd()
  omit: ['Array.prototype.includes'], // Defaults to []
  hostname: 'example.com',            // Defaults to 'polyfill.io'
  unknown: 'polyfill',                // Defaults to null. Accepts 'polyfill' or 'ignore'
  useComputeAtEdgeBackend: 'yes',     // Defaults to null. Accepts 'yes' or 'no'
  flags: 'gated',                     // Defaults to null. Accepts 'always', 'gated' or both ['always', 'gated']
});

Contributing

This module has a full suite of unit tests, and is verified with ESLint. You can use the following commands to check your code before opening a pull request:

npm test    # verify JavaScript code with ESLint and run the tests

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

Publishing

New versions of the module are published automatically by CI for every commit which lands on the master branch.

Authors

See also the list of contributors who participated in this project.

Contact

If you have any questions or comments about this module, or need help using it, please raise an issue.

Licence

This project is licensed under the MIT License - see the LICENSE.md file for details