Question 1

How to watch files and restart processes with Foy?

Accepted Answer

Use ctx.monitor() in tasks to monitor directories and execute commands on changes. For example, ctx.monitor('./src', 'node ./dist') will restart the node process when files in ./src change, as shown in the watch and build section.

Question 2

Foy vs Gulp: which is better for TypeScript projects?

Accepted Answer

Foy excels with its promise-based API and type-safe options, making it ideal for clean TypeScript code. Gulp has a larger plugin ecosystem but more boilerplate. Choose Foy for simplicity and TypeScript focus, Gulp for extensive pre-built plugins.

Question 3

How to run tasks in parallel in Foy?

Accepted Answer

Define task dependencies with the async option, like dep('task').async(), or use Promise.all with ctx.exec for concurrent command execution. The README shows examples with async() for parallel dependencies.

Question 4

Does Foy integrate with npm scripts?

Accepted Answer

Yes, Foy can execute npm commands via ctx.exec, and you can call it from package.json scripts. However, it's designed as a standalone runner, so integration might require manual setup for seamless workflow.

Question 5

How to handle errors in Foy tasks globally?

Accepted Answer

Use the onerror lifecycle hook to catch errors across all tasks, or wrap specific task logic in try-catch blocks. The README demonstrates onerror() for error handling in namespaces.

Question 6

Foy or plain npm scripts for simple builds?

Accepted Answer

Foy offers more structure with dependencies and TypeScript support, while npm scripts are simpler for basic tasks. Use Foy when you need complex orchestration, type safety, or file watching beyond npm scripts' capabilities.

foy

What is foy?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions