2022-04-26
1513
#typescript#webpack
Iva Kop
105646
Apr 26, 2022 â‹… 5 min read

How to detect dead code in a frontend project

Iva Kop I am a self-taught software developer passionate about frontend development and architecture.

Recent posts:

Go Design Pattern Article Image With Logo

Why Go design patterns still matter

Here’s how three design patterns solved our Go microservices scaling problems without sacrificing simplicity.

Peter Aideloje
Aug 28, 2025 â‹… 2 min read
how to protect your ai agent from prompt injection attacks

How to protect your AI agent from prompt injection attacks

Explore six principled design patterns (with real-world examples) to help you protect your LLM agents from prompt injection attacks.

Rosario De Chiara
Aug 27, 2025 â‹… 5 min read
Don’t Let AI Erase The Next Generation Of Dev Leaders

Don’t let AI erase the next generation of dev leaders

As AI tools take over more routine coding work, some companies are cutting early-career dev roles — a short-sighted move that could quietly erode the next generation of tech leaders if we aren’t careful.

Jack Herrington
Aug 26, 2025 â‹… 6 min read

Qwen3-Coder: Is this Agentic CLI smarter than senior devs?

Discover Qwen3-Coder, Alibaba’s 480B parameter agentic coding CLI, with real-world tests, use cases, and performance insights.

Chizaram Ken
Aug 26, 2025 â‹… 4 min read
View all posts

3 Replies to "How to detect dead code in a frontend project"

  1. Great article! 👍

    Regarding this part 👇

    > The plugin will report unused files and unused exports into your terminal but those are not part of your webpack build process, therefore, it will not fail your build

    According to their docs, there is a way `failOnHint` to fail the build if the `webpack-deadcode-plugin` finds something.

    > options.failOnHint (default: false)
    > Deadcode does not interrupt the compilation by default. If you want to cancel the compilation, set it true, it throws a fatal error and stops the compilation.

    https://github.com/MQuy/webpack-deadcode-plugin#optionsfailonhint-default-false

  2. One small remark 🙂

    You don’t need to install depcheck before `npx depcheck`. There are just two options: do `npm i -g depcheck` or `npx depcheck`

Leave a Reply