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

copytotheplace

v0.1.1

Published

Utility to copy files to a configurable and variable place

Downloads

28

Readme

copytotheplace

In my project pipelines I often have to copy my compiled files to a special directory after the build process completes. That's easy. But the location of the special directory depends on my local file system and isn't part of the project directory, so it needs to be configurable per local copy.

This tool will allow setting the destination directory using an environment variable, config file, or on the command line.

If no destination directory is set, this tool will do nothing, which allows this to be used as the last step in a pipeline without doing anything unless called-for.

Install

To install globally:

npm install -g copytotheplace

To install for a project:

npm install --save-dev copytotheplace

Usage

IMPORTANT NOTE: copytotheplace intentionally fails silently if no destination directory is set. You can set the destination directory on the command-line, via the COPYTOTHEPLACE environment variable, or by writing COPYTOTHEPLACE=<some directory> to a .env file in the directory where it is run.

Command-line

This will copy the file build/index.js to dist/index.js:

copytotheplace --place dist build/index.js

You can omit the --place option if you set the COPYTOTHEPLACE environment variable:

COPYTOTHEPLACE=dist copytotheplace build/index.js

You can save the environment variable by putting it in a .env file:

echo 'COPYTOTHEPLACE=dist' > .env

then:

copytotheplace build/index.js

As a node module

This will copy the file build/index.js to dist/index.js:

// ES2015:
import { copytotheplace } from 'copytotheplace'
copytotheplace( [ 'build/index.js' ], 'dist' )
// ES5:
var copytotheplace = require( 'copytotheplace' ).copytotheplace;
copytotheplace( [ 'build/index.js' ], 'dist' );

You can omit the second argument to copytotheplace() if you set the COPYTOTHEPLACE environment variable. You can save the environment variable by putting it in a .env file:

echo 'COPYTOTHEPLACE=dist' > .env

then, in your code:

// ES5:
copytotheplace( [ 'build/index.js' ] );