feat(frontend): Storybook setup, component stories, config and error …

[A6dulmalik]

…utilities (#94, #96, #97, #99)

• Add lib/config.ts: centralise SDK_URL and API_KEY from env with dev fallback (Environment config: SDK base URL and API key injection #94)
• Add lib/errors.ts: BridgeletApiError class with status, message, userMessage (Typed API error class for all SDK responses #99)
• Add lib/sdk.ts: createClaim, getClaimStatus, redeemClaim wrappers using config + errors
• Configure Storybook 8 with nextjs-vite, addon-docs, addon-a11y, chromatic (Set up Storybook for UI component development #96)
• Add stories for ClaimStatusCard, SendFormStep, ToastNotification, WalletAddressInput, SkeletonLoader with autodocs and all variants (Document all reusable components in Storybook #97)
• Update .env.example with NEXT_PUBLIC_SDK_URL and NEXT_PUBLIC_API_KEY

Executive Summary

Linked Issues & References

• Issue: Resolves #
• Related PRs:

Type of Change

Category

• New Feature (Non-breaking change adding functionality)
• Bug Fix (Non-breaking change fixing an issue)
• Performance Optimization (Code change to improve efficiency)
• Refactoring (Code structure change without external API modification)
• Security Patch (Fixing a vulnerability or security concern)
• Documentation (Updates to README, Wiki, or inline docs)
• Infrastructure (CI/CD, build scripts, Docker)

Domain

• Smart Contracts (Rust/Soroban)
• SDK/Backend (NestJS/TypeScript)
• Frontend/UI

Technical Implementation Details

Breaking Changes

• No - Backward compatibility is maintained.
• Yes - This change requires consumers of the SDK/Contract to update their code.

Verification & Testing Strategy

Automated Tests

• Unit Tests: Added/Updated new unit tests.
• Integration Tests: Verified interaction between modules.
• Linting: Code follows the project's style guide.

Manual Verification

1. Environment:

• Target Environment:

2. Reproduction Steps:

3. Proof of Execution:

Quality Assurance Checklist

• I have performed a self-review of my own code.
• I have commented on my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect these changes.
• My changes do not generate new warnings or errors.
• I have verified that new dependencies are necessary and secure.
• (If Smart Contract) I have verified gas usage and storage footprints are optimized.

---

By submitting this Pull Request, I acknowledge that I have adhered to the Bridgelet contribution guidelines.

Closes #94,
Closes #96,
Closes #97,
Closes #99

[drips-wave]

@A6dulmalik Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits