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

copy-for-browser

v2.0.3

Published

Copy files from node-modules to a public path for use in the browser

Downloads

2

Readme

copy-for-browser

Copy files from node_modules to a public path for use in the browser

This utility is designed to be used where you have both a server and a browser client being loaded from the same tree.

It will copy files from under node_modules to the correct directory in the public path, based on the package.json for the package.

Install

npm install copy-for-browser --save-dev

Usage

In your package.json, your will need a section at the top level with the key "browserCopy". This should contain one or more keys which are destination paths for the files. Each key should have an array of file paths for the source files.

This is a (simplified) example of package.json:

{
  "name": "my-package",
  "dependencies": {
    "jquery": "^3.2.1",
    "jquery-ui": "^1.12.1",
  },
  "dev-dependencies": {
    "copy-for-browser": "^1.0.0"
  },
  "browserCopy": {
    "public/js/vendor": [
      "jquery/dist/jquery.min.js",
      "pouchdb/dist/pouchdb.min.js"
    ],
    "public/css": [
      "jquery-ui/themes/base/all.css"
    ]
  },
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "copy": "copy-for-browser"
  }
}

Using this, you can run npm install and npm run copy and the files will appear in public/js/vendor and public/css, relative to the root of your project.

Please let me know if you find this useful. Any issues or comments would be appreciated at Github.

Note

In version 1.x of copy-for-browser, the key "browser" was used. This has been changed to "browserCopy" to avoid the conflict with browserify.