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:

Exploring The Top Rust Web Frameworks

Exploring the top Rust web frameworks

In this article, we’ll explore the best Rust frameworks for web development, including Actix Web, Rocket, Axum, warp, Leptos, Cot, and Loco.

Abiodun Solomon
May 28, 2025 â‹… 11 min read
How To Use The CSS Cursor Property

How to use the CSS cursor property

A single line of CSS can change how users feel about your UI. Learn how to leverage the cursor property to signal intent, improve interaction flow, and elevate accessibility.

Chizaram Ken
May 28, 2025 â‹… 6 min read
Build TypeScript App Vite

How to build a React + TypeScript app with Vite

We explore the benefits of building an app with React, TypeScript, and Vite, and compare its performance to the same app built with CRA.

Clara Ekekenta
May 28, 2025 â‹… 7 min read

How to use Claude to build a web app

Learn how to build a weather app using Claude, from setting up infrastructure to creating a functional UI that displays city-based forecasts.

Andrew Evans
May 28, 2025 â‹… 8 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