feat: Add Twitter share buttons for listing, purchase, staking & rewards + formatting & hydration fixes #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


📝 Pull Request Description
This PR adds social sharing functionality across key user actions on RegenBazar to drive visibility and engagement on X (formerly Twitter). It also includes formatting and hydration-related fixes.
✨ Features Added
✅ TweetButton Component
Created a reusable TweetButton at:
src/components/TweetButton.tsx
→ Leverages Twitter Web Intent for sharing pre-written tweet content in one click.
📤 Integrated TweetButton on:
app/create-nonprofit-profile/page.tsx: after a nonprofit (Seller) lists a product
app/project/page.tsx: after a Buyer purchases a product
app/stake/page.tsx: after staking RWIP NFTs
app/stake/page.tsx: after earning staking rewards
🔗 All tweets link to: https://regenbazar.com/ to promote the platform (or whatever the actual domain will be)
🧹 Cleanup & Fixes
🧼 Ran npx prettier --write . across the project for consistent code formatting
🛠️ Fixed minor hydration mismatch warnings in dynamic pages like /stake
While testing on Brave browser, I encountered an issue where the app prompts to "Install MetaMask" despite MetaMask already being installed.
This could be due to Brave's built-in Web3 wallet interfering with the MetaMask detection logic — needs further investigation.