web(Header): ensure named icon imports from lucide-react

[pragmaticAweds]

Summary

Wildcard import patterns inflate client bundle size.

Where

apps/web/src/components/layouts/Header.tsx:5-15

Why this is a real bug, not just lint noise

1. Affects user experience, functionality, or performance in production.
2. Needs to be addressed to ensure robustness across all supported devices and Stellar network states.

Fix

Use direct named icon imports to facilitate tree-shaking.

Acceptance criteria

• Issue is resolved in apps/web/src/components/layouts/Header.tsx:5-15.
• No regression introduced in existing test suites.

[oyinade247]

@oyinade247 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Allow me fix this quickly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @oyinade247 to this issue.

[utilityjnr]

@utilityjnr has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

i would love to solve this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @utilityjnr to this issue.

[AbuTuraab]

@AbuTuraab has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi,

I’d like to request assignment to this issue.

As a full-stack developer working actively in the Stellar ecosystem, I understand how important robust automation is for projects that combine Soroban smart contracts, backend services, and frontend applications. A reliable CI/CD pipeline is the backbone of safe contract development, deterministic builds, and predictable testnet releases.

During the previous waves of contributions, I worked on several Stellar-related repos where I resolved issues such as:
Frontend implementations.
Misconfigured GitHub Actions leading to failing builds
Missing or incomplete Soroban contract test pipelines
Frontend pipelines that didn’t catch build/lint errors
Inefficient caching (Rust, pnpm) that slowed down CI
Incorrect workflow permissions affecting deployment and artifact uploads
These issues helped me develop a strong sense of what healthy CI/CD should look like for blockchain projects.

Relevant Skills
Full-stack expertise with Soroban, Rust, TypeScript, and modern frontend tooling
Strong experience designing and maintaining GitHub Actions workflows
Familiar with contract testing, reproducible builds, and blockchain dev best practices
Experience with pnpm-based frontend CI pipelines (install, lint, type-check, build)
Comfortable implementing secure deployment flows, secret management, and workflow permission hardening
Confident in making pipelines faster and more reliable using smart caching strategies

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AbuTuraab to this issue.

[devchant]

@devchant has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hey, can I solve this? I'll start by familiarizing myself with the relevant modules and dependencies before implementing the feature in a clean and scalable way. My goal is to produce a well-tested solution that blends naturally with the existing codebase.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devchant to this issue.

[drips-wave]

Congratulations, @AbuTuraab! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @AbuTuraab: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[AbuTuraab]

Hi @pragmaticAweds please can you update this codebase, Header.tsx is not currently existing at all.