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:

Wasm 3 Before GTA 6 LogRocket Article

We got Wasm 3.0 before GTA 6: Meet the web’s new engine

Discover how WebAssembly 3.0’s garbage collector, exception handling, and Memory64 transform Wasm into a true mainstream web platform.

Ikeh Akinyemi
Oct 3, 2025 ⋅ 2 min read

How to use AI to build accurate ShadCN components

AI agents often break shadcn/ui components with outdated docs or made-up props. The MCP server fixes this by giving live access to registries. In this tutorial, we’ll set it up and build a Kanban board to show it in action.

Chizaram Ken
Oct 3, 2025 ⋅ 5 min read
Rust Project for Web Services LogRocket Article

The best way to structure Rust web services

Learn how to structure Rust web services with clean architecture, Cargo workspaces, and modular crates for scalable, maintainable backends.

Jude Miracle
Oct 2, 2025 ⋅ 2 min read
andrew evans headshot

A spec-first workflow for building with agentic AI

Andrew Evans gives his take on agentic AI and walks through a step-by-step method to build a spec-first workflow using Claude Code.

Andrew Evans
Oct 1, 2025 ⋅ 18 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