[Dashboard] - Refactor Project Structure

[KirillKirill]

Issue tracking

Not ticketed

Context behind the change

We wanted to rewrite the project using some established solution for architecture in order to make the app's code better.
The Feature Sliced Design fits in well for the app. You can read about this architecture here.
Now we have a feature oriented structure of the project, where an each meaningful feature absorbs all the necessary assets around itself and make the structure more clear and straightforward.
The components/helpers that are supposed to be reused across the app are now located in the shared directory.
Each page looks like a high level constructor, that only imports a linked feature and UI widgets.

Other changes:

• added tsc check to lint script and pre-commit hook
• removed a lot of assets, that are never used anymore (mostly chain icons), and removed svgr package
• used export default, if it's possible (almost always)
• used camelCase instead of kebab-case
• refactored query hooks such, that they don't depend on zustand store
• created usePagination hook for the tables within the search feature

A comparison of previous structure and current:

Before	After

How has this been tested?

Locally; I've made sure the functionality remains intact

Release plan

regular plan

Potential risks; What to monitor; Rollback plan

I only might've missed something that stoped working after restructuring

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
human-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:41am
human-dashboard-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:41am
staking-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 24, 2025 9:41am

2 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
faucet-frontend	⬜️ Ignored (Inspect)	Visit Preview		Jun 24, 2025 9:41am
faucet-server	⬜️ Ignored (Inspect)	Visit Preview		Jun 24, 2025 9:41am

[dnechay]

Nice work!

Some suggestions:

1. Maybe we move shared/lib/env to shared/config/env? We don't have some utilities for env, just config parsing and validation, so it feels more natural to look for it in some env or config path, rather than lib
2. I'm not entirely sure about removing index.ts files in places like shared/lib. The only benefit I see (but might miss something) of having libs as "one-per-file" and importing them directly is tree-shaking, but in this particular case it looks like we use majority of them altogether, so there will be no practical improvement. Anyway, we can keep such approach for shared libs and group them later for better structure (e.g. import formatHmtDecimals from shared/lib/formatters/hmtDecimals), but keep index.ts files for libs in features, because it's supposed to load altogether (features/graph as for example)
3. Not related to this PR, but in general: maybe in future we get id of extra requests for getting lastPageIndex and change API to return hasMore: boolean, just as an idea