depchecker VS browserslist

Therefore, one workaround I found to reduce the bundle size is with the use of a library named **depcheck**. We can install the package by

Another package we use for optimization helps us generate a list of unused npm packages. Then we manually go through the list and remove everything unnecessary, thereby reducing the project's weight and organising things.

While we’re on the subject of dead code detection, let’s briefly discuss how to ensure we don’t have unused dependencies in our project. Let’s use depcheck, a tool for analyzing the dependencies in a project. It can tell us:

I know it has been asked before, but depcheck doesn't seem to work for me at all. It gives me a ton of false alerts aparts from having to configure it for "config-only" libs like babel, eslint etc.

You can use depcheck for that https://www.npmjs.com/package/depcheck no need to do that manually.

Try npx depcheck - https://www.npmjs.com/package/depcheck

You can follow the packages below: depcheck unimported

There is a module called depcheck. I have never used it but probably it’s what you are looking for

I run this https://github.com/TheJaredWilcurt/depchecker

Not these days, where most people are using evergreen browsers and iOS users upgrade very quickly.

Take a look at the defaults for browserslist, for example:

https://browsersl.ist/#q=defaults

It just barely supports Safari 15, on iOS only, and that’s likely to go away imminently because it’s under 1% usage.

browserslist

We compile JS only for modern browsers. The list of default browsers in Next can be overridden in your browserslist.

In the latest versions of Next.js, targeting specific browsers or features is a breeze using the Browserslist configuration in your package.json file. The latest version of Next.js (v13) uses the following configuration by default:

For a more general answer to browser support, check out https://github.com/browserslist/browserslist. That seems to be standard tool to help you with that.

As someone else pointed out, you're overestimating Chrome/ium's market share.

Regardless, after the web.dev/baseline announcement, I looked at Browslerlist and one of our site's analytics and it is shocking how many people are not using the last two versions of evergreen browsers. There is a long tail of browser versions in those stats.

https://browsersl.ist

The way folks handle this in production is with browserslist, which lets you query on different things you want to support: https://github.com/browserslist/browserslist. This in turn tells other parts of your tooling what language features to transpile for production.

I imagine tools could be built on top of that which do what you’re asking too

# .browserslist.rc # Babel Preset configuration # -------------------------- # Defines web-browser compatibility parameters for Babel to transpile your JS code. # This configuration is used by babel.config.js. # More information in here. # https://github.com/browserslist/browserslist # Support browsers with a market share higher than 5% >10%