Sharing hooks with the team (husky) in Git - Practice Problems & Coding Challenges

Challenge - 5 Problems

💻 Command Output

intermediate

What is the output of installing Husky with the correct command?

You run the command npm install husky --save-dev in your project. What is the expected output message you should see to confirm Husky installed successfully?

A husky is not recognized as an internal or external command

B error: command not found: husky

C npm ERR! missing script: husky

D added 1 package, and audited 1 package in 2s

💡 Hint

Look for the message that confirms a package was added without errors.

When you install Husky using npm, the output shows that a package was added and audited. Errors or missing commands indicate installation problems.

🔀 Workflow

intermediate

Which step correctly sets up Husky hooks to be shared with the team?

After installing Husky, which command should you run to initialize Husky hooks so they are tracked in your Git repository and shared with your team?

A npx husky install

B git init

C npm start

D husky add .husky/pre-commit "npm test"

💡 Hint

This command creates the hooks folder and sets up Git hooks.

Running npx husky install creates the .husky folder and sets up Git hooks so they can be shared via the repository.

❓ Configuration

advanced

Which package.json script ensures Husky hooks are installed automatically after cloning?

You want Husky hooks to be installed automatically when a team member clones the repo and runs npm install. Which package.json script configuration achieves this?

A "prepare": "husky install"

B "postinstall": "husky install"

C "preinstall": "husky install"

D "install": "husky install"

💡 Hint

This script runs automatically after dependencies are installed and before publishing.

The prepare script runs after npm install and is the recommended place to run husky install so hooks are set up automatically.

❓ Troubleshoot

advanced

Why does the Husky hook not run after cloning the repo?

A team member cloned the repo and ran npm install, but Husky hooks do not run on Git commits. What is the most likely cause?

A Git is not installed on the team member's machine

B The .husky folder is ignored by .gitignore

C The <code>prepare</code> script is missing in package.json, so hooks were not installed

D The team member did not run <code>npx husky add</code> manually

💡 Hint

Check if the hooks installation step runs automatically after install.

Without the prepare script running husky install, hooks are not set up after cloning and installing dependencies.

✅ Best Practice

expert

What is the best way to share a new pre-commit hook with your team using Husky?

You want to add a new pre-commit hook that runs npm test and share it with your team. Which sequence of commands and steps is best practice?

A Create a shell script with tests and share it via email

B Run <code>npx husky add .husky/pre-commit "npm test"</code>, commit the .husky folder, and push to the repo

C Run <code>npx husky install</code> on your machine only, no commit needed

D Add <code>npm test</code> to package.json scripts, then tell team to run it manually

💡 Hint

Think about how Git tracks files and how Husky hooks are stored.

Husky hooks live in the .husky folder which must be committed and pushed. Adding the hook with npx husky add creates the file. This ensures all team members get the hook after pulling.