Install Vercel Web Analytics integration - #2
Draft
vercel[bot] wants to merge 415 commits into
Draft
Conversation
Each recent mint tile now links to its token page and keeps the token ID visible directly beneath the image for quick access. Made-with: Cursor
Register four new hand overlays in the backend composer and expose them with clear labels in the Hand dropdown so they can be selected in the editor. Made-with: Cursor
Keep the render status text centered inside the asset frame and ensure the token ID suggestion dropdown stays above lower controls. Made-with: Cursor
Prevent token suggestions from overlapping other controls by rendering the list in normal flow and refresh dropdown styling with a cleaner responsive two-column layout. Made-with: Cursor
Stabilize dropdown card spacing to prevent section overlap and convert the four Dr. Bombay hand PNG backgrounds to transparency for clean compositing. Made-with: Cursor
Keep Dr. Bombay entries at the top of the Hand list and enforce readable text colors for dropdown headers and latest mint labels against dark surfaces. Made-with: Cursor
This captures the latest frontend styling and app behavior refinements, etherscan service adjustments, backend app tweak, and regenerated production build outputs. Made-with: Cursor
Wire the glitter cowboy hat option to its backend asset and fix a missing comma in the specific hats set so plunger/special-hat checks behave correctly. Made-with: Cursor
Expand the Minted AFAs panel to list all minted tokens with lazy-loaded previews, and load the clicked token into the editor instead of linking out. Co-authored-by: Cursor <cursoragent@cursor.com>
Replace sticky preview behavior on small screens so editing panels scroll smoothly, while keeping quick actions pinned above the safe area. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the ape visible while scrolling panels without pinning Reset, Randomize, and Frame It to the bottom of the screen. Co-authored-by: Cursor <cursoragent@cursor.com>
Add afa-editor.app CORS origins and apply tokenId/trait query params when opening the editor from mint or share links. Co-authored-by: Cursor <cursoragent@cursor.com>
Enforce mint checks on the API and frontend, and link unminted token IDs to apefacingapes.com/claim. Co-authored-by: Cursor <cursoragent@cursor.com>
Return newest mints first from the API, dedupe IDs consistently, and use the mint set for the displayed count. Co-authored-by: Cursor <cursoragent@cursor.com>
Refresh afa_db from Etherscan, prefer on-chain mint data when stale, and let users sort the gallery by mint date or token ID. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the sort control on the same row as the Minted AFAs title so the gallery uses no extra vertical space. Co-authored-by: Cursor <cursoragent@cursor.com>
Override inherited center text alignment so the title stays flush left while the sort control remains on the right. Co-authored-by: Cursor <cursoragent@cursor.com>
Apply selected hat assets after trait composition so editor hat picks render on apes that have no original hat layer. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Show the cached mint list immediately and refresh from Etherscan in the background only when needed. Co-authored-by: Cursor <cursoragent@cursor.com>
Reuse face.png favicon assets and JS frame cycling from the mint progress app for consistent branding across both sites. Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…pp Engine. Co-authored-by: Cursor <cursoragent@cursor.com>
Surface apefacingapes.com and afa-progress.com in the footer so users can reach minting and the grid view from the editor. Co-authored-by: Cursor <cursoragent@cursor.com>
# Vercel Web Analytics Implementation
## Summary
Successfully installed and configured Vercel Web Analytics for the AFA Builder React application following the latest official Vercel documentation.
## Changes Made
### 1. Package Installation
- **Added dependency**: `@vercel/analytics@^2.0.1` to `frontend/package.json`
- **Updated**: `frontend/package-lock.json` with the new dependency tree
- **Installation method**: Used npm with `--legacy-peer-deps` flag to resolve peer dependency conflicts with existing TypeScript versions
### 2. Code Configuration
**Modified file**: `frontend/src/App.js`
- **Import added**: `import { Analytics } from '@vercel/analytics/react';`
- **Component added**: `<Analytics />` component placed just before the closing `</div>` tag in the App component's return statement, right after the `<Footer />` component
## Implementation Details
### Framework Detection
- **Framework**: React 18.2.0 with Create React App (react-scripts 5.0.1)
- **Package Manager**: npm (confirmed by presence of `package-lock.json`)
### Documentation Reference
Fetched the latest installation instructions from the official Vercel Analytics documentation:
- URL: https://vercel.com/docs/analytics/quickstart
- Followed React-specific setup instructions
- Placed the Analytics component in the root App component as recommended
### Verification Steps Completed
1. ✅ **Build Test**: Successfully built the project with `npm run build`
- Build completed without errors
- Bundle size increased by 1.51 kB (expected for analytics library)
2. ✅ **Test Suite**: Ran test suite with `npm run test --watchAll=false --passWithNoTests`
- No test failures
3. ✅ **Linting**: Build process includes ESLint validation - no errors reported
## Files Changed
- `frontend/package.json` - Added @vercel/analytics dependency
- `frontend/package-lock.json` - Updated with new dependency tree
- `frontend/src/App.js` - Added Analytics import and component
## Next Steps
To complete the setup:
1. Deploy the application to Vercel
2. Enable Web Analytics in the Vercel project dashboard (Analytics tab → Enable button)
3. Verify analytics tracking by checking browser Network tab for requests to `/<unique-path>/view` after deployment
4. Monitor analytics data in the Vercel dashboard
## Notes
- The Analytics component is lightweight and will only collect data when deployed on Vercel
- No additional configuration is needed for basic page view tracking
- Custom events can be added later if needed (available on Pro/Enterprise plans)
- The component is non-invasive and won't affect existing functionality
Co-authored-by: Vercel <vercel[bot]@users.noreply.github.com>
Author
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Vercel Web Analytics Implementation
Summary
Successfully installed and configured Vercel Web Analytics for the AFA Builder React application following the latest official Vercel documentation.
Changes Made
1. Package Installation
@vercel/analytics@^2.0.1tofrontend/package.jsonfrontend/package-lock.jsonwith the new dependency tree--legacy-peer-depsflag to resolve peer dependency conflicts with existing TypeScript versions2. Code Configuration
Modified file:
frontend/src/App.jsimport { Analytics } from '@vercel/analytics/react';<Analytics />component placed just before the closing</div>tag in the App component's return statement, right after the<Footer />componentImplementation Details
Framework Detection
package-lock.json)Documentation Reference
Fetched the latest installation instructions from the official Vercel Analytics documentation:
Verification Steps Completed
npm run buildnpm run test --watchAll=false --passWithNoTestsFiles Changed
frontend/package.json- Added @vercel/analytics dependencyfrontend/package-lock.json- Updated with new dependency treefrontend/src/App.js- Added Analytics import and componentNext Steps
To complete the setup:
/<unique-path>/viewafter deploymentNotes
View Project · Web Analytics
Created by Cophi (cophi-dev) with Vercel Agent