Question 1

How do I exclude test files when copying with copyfiles?

Accepted Answer

Use the -e option with a glob pattern. For example: copyfiles -e "**/*.test.js" -f ./src/**/*.js ./dist will copy all JS files to dist, flattening the structure and excluding test files.

Question 2

copyfiles vs cp command: which should I use?

Accepted Answer

copyfiles is better for complex, cross-platform copying with glob patterns and path manipulation in Node.js environments. Use native cp for simple, one-off copies without advanced features.

Question 3

Does copyfiles work with symbolic links?

Accepted Answer

Yes, but only with the --follow flag. By default, it might not resolve symlinks; adding -F ensures linked files are copied, which is useful in development workflows.

Question 4

Can I use copyfiles in npm scripts for build processes?

Accepted Answer

Absolutely. Install it as a dev dependency and reference it in package.json scripts. For instance: "copy:assets": "copyfiles -f ./assets/**/* ./public" automates asset copying.

Question 5

How to flatten all files from nested directories into one folder?

Accepted Answer

Use the --flat or -f flag. For example: copyfiles -f ./data/**/*.json ./output merges all JSON files from nested directories into the output folder.

Question 6

What are common pitfalls when using copyfiles on Windows?

Accepted Answer

Globs must be double-quoted, and home directory paths starting with tilde require -u or -f to avoid errors. Always check the README for Windows-specific syntax.

copyfiles

What is copyfiles?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions