eslint-plugin-import

https://github.com/import-js/eslint-plugin-import/blob/HEAD/... It's not built in to ESLint, but it's fairly widely used in my experience and helps ensure that you've got a sensible split between production and non-production.

I recently came across this issue (https://github.com/import-js/eslint-plugin-import/issues/213... and https://github.com/import-js/eslint-plugin-import/issues/181...) and man that person has really found him self a hill. What is a bit worrying though is that he is an active member and contributor to TC-39. Meaning that this kind of community hostility is very much alive among the people who rule JavaScript.

There is some interesting [drama][1] with this, since this article noticeably doesn't mention any PRs they opened to remove some of these older polyfills. The reason those PRs were never opened/merged is the maintainer of many of those libraries [has a strong stance on "breaking" changes][2] in software: > I have developed an intense avoidance for breaking changes in all of my packages, because I don't want to inflict hundreds of millions of dollars of person-hour cost on the entire industry unnecessarily. IMO this argument avoids the opposite claim, that people then spend a ton of time (and money) trying to make old tech work with newer tech since not everyone maintains to the same standards of backwards compatibility. But regardless, no one is required to stick to a particular way of creating open source software, so the one benefit her

Thanks, happy you enjoyed the article! The PRs for the previous article were all merged. I originally wanted to do the same for this one, but I'm not sure if I have the time to fix all of them. Updating to a newer version of `resolve` already addresses the most notable issue with throwing more errors than necessary, but many parts of the ecosystem still use an old version. Manged to land this PR in another package though https://github.com/import-js/eslint-import-resolver-typescri... . Performance there could be easily improved further there. Another PR to an eslint plugin was unfortunately rejected as it broke node 4 support https://github.com/import-js/eslint-plugin-import/pull/2654 . The other popular package that's used for module resolution is `enhanced-resolve` by the webpack folks and they expect the consumer to deal with passing t

There's an eslint plugin to detect circular dependencies: https://github.com/import-js/eslint-plugin-import/blob/main/...

I've been using DPDM: https://github.com/acrazing/dpdm These are my package.json scripts for detecting cycles: "cycles": "run-p cycles:client cycles:server", "cycles:client": "dpdm client/src/\*/\*.ts --exit-code circular:1", "cycles:server": "dpdm server/src/server.ts --exit-code circular:1", The exit code is set like that so that the CI will fail on cycles, since we run this in our CI build. I also hear people use ESLint, probably this: https://github.com/import-js/eslint-plugin-import/blob/main/... The fact that the compiler itself doesn't error on cycle imports, and that the errors caused by those imports are so opaque, seems like an oversight to me.