🚀 This is the first post in a series about the small frontend habits that make a big impact — starting with ✨ import sorting ✨
Coming soon:
📁 file naming
🏗️ project structure
<a href="https://medium.com/@things-to-know/why-import-sorting-matters-50feb8747262" target="_blank" rel="noopener nofollow">👉Why Import Sorting Matters</a>

Full-Stack Developer sharing my knowledge through my series ThingsToKnow. Coding enthusiast, lifelong learner and problem solver linkedin.com/in/sabajanelidze

Things To Know

Import sorting is emphasized as a significant habit for clean code in frontend development, enhancing readability and maintainability. This post is part of a series focusing on impactful frontend practices.

Why Import Sorting Matters (Clean Code Series #1)

After 30 years of coding, and over a decade obsessing about import order I can say now it is utterly irrelevant.
Also your example has NOTHING to do with imports sorting, its just basic tree-shaking issue, unrelated at all to the topic of your article:
<img src="https://media.daily.dev/image/upload/s--mDWuqxfT--/f_auto/v1745422888/ugc/content_793ec2d1-3b79-41b9-9748-7705941582de" alt="image">

not touching any codebase where the imports aren’t shorted

Great Share, My current project is following to this way. Btw, I have never thought this would work so well.

You guys are crazy, I’ll have like 20 unused imports, and I’m not sorting the ones I use, thanks.