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

temp-dir-cp

v1.0.1

Published

Copy folder temp location

Downloads

4

Readme

temp-dir-cp

NPM version Build Status XO code style

⚡️ Copy folder to a unique temp location

Install

yarn add temp-dir-cp
# same as npm install --save

Usage

Assume that in the current directory, there is a directory called fixtures:

$ tree
.
├── fixtures
│   └── file.txt
└── index.js

Call temp-dir-cp with "fixtures"

// index.js
const tempDirCp = require('temp-dir-cp');

tempDirCp('fixtures');
//=> '/var/folders/6r/cyh35ykj4h77jnn0lz0xqx580000gn/T/87166550876/fixtures'

tempDirCp('fixtures');
//=> '/var/folders/6r/cyh35ykj4h77jnn0lz0xqx580000gn/T/75704852254/fixtures'

Both of these newly created directory's have the contents of the fixtures directory. Each can be mutated separately without affecting one another or the source.

$ tree /var/folders/6r/cyh35ykj4h77jnn0lz0xqx580000gn/T/87166550876
└── fixtures
    └── file.txt

$ tree /var/folders/6r/cyh35ykj4h77jnn0lz0xqx580000gn/T/75704852254
└── fixtures
    └── file.txt

For any tests which modify the file-system, you can't cd into your fixtures and then run the tests. That would modify your fixtures and therefore break future tests. Use tempDirCp instead and you will have a fresh copy of your files in a unique directory every time. The unique directory is temporary too, so it gets removed on computer startup!

API

tempDirCp(sourceDir)

Arguments

| Name | Description | Type | Default | | ------- | ------------------------------- | -------- | ------- | | sourceDir | Directory that should be copied | string | None |

Returns

Type: string

License

MIT © Dawson Botsford