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-production-deps

v0.2.2

Published

Create production node_modules from Npm/Yarn workspace

Downloads

17

Readme

Copy node production deps

npm Build status codecov

Find and copy production deps of package living in yarn workspace to dist folder.

NOTE: This is very experimental package., nevertheless it's used in one internal project to build minimal node_modules for services running in docker.

Usage

# copy deps of current folder to ./dist
$ npx copy-production-deps

# copy deps specific package to specific folder
$ npx copy-production-deps packages/foo-backend dist/foo-backend

# Only dist selected packages that are not bundled with esbuild
$ esbuild server.js --outfile dist/server.js --external:mongoose --external:hiredis
$ npx copy-production-deps . dist --only-packages mongoose,hiredis

Doc

Full synopsis:

copy-production-deps [packageDir] [distDir]

copy production deps from Npm/Yarn workspace to dist folder

Positionals:
  packageDir  source package folder (must contain package.json)   [default: "."]
  distDir     distribution directory (packages will be copied to
              ${distDir}/node_modules)                       [default: "./dist"]

Options:
  --version       Show version number                                  [boolean]
  --dryRun, -n    Dry run - only show what would be copied.
                                                      [boolean] [default: false]
  --verbose, -v   Run with verbose logging            [boolean] [default: false]
  --exclude-from  Read ecluded file patterns from file one pattern a line.
                                                           [array] [default: []]
  --exclude       Exclude file pattern (minimatch glob)    [array] [default: []]
  --only-packages Include only those packages         [array] [default: []
  --help          Show help                                            [boolean]

Why

Born from frustration that both yarn and npm have several bugs related to --production install and i almost wrote everywhere before i found copy-node-modules which apparently didn't support yarn workspaces.

Contribute

PRs accepted.

License

MIT © Zbigniew Zagórski