feat: add Next.js playground with turborepo integration

[abretonc7s]

Description

This PR builds on #1195 to introduce a new Next.js playground package leveraging the turborepo setup.

Dependencies

⚠️ Requires PR #1195 to be merged first.

Key Changes

• Added new playground-next package with Next.js 15.1.4
• Basic MetaMask integration example with workspace dependencies
• Simple wallet connection demo
• Added package to workspace config

Benefits

• Modern playground environment with proper hot reload
• Direct workspace dependencies instead of transpiled references
• Streamlined development workflow building on turborepo setup

Implementation Details

• Next.js app setup with MetaMaskProvider
• Basic wallet connection example
• Proper TypeScript and ESLint configuration
• Workspace dependency on @metamask/sdk-react

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/[email protected]	None	0	20.6 kB	types
npm/@types/[email protected]	None	0	800 kB	types
npm/[email protected]	Transitive: environment, filesystem, unsafe	+29	10.5 MB	vercel-release-bot
npm/[email protected]	environment, filesystem, network, shell, unsafe Transitive: eval	+33	1.45 GB	rauchg, timneutkens, vercel-release-bot
npm/[email protected]	Transitive: environment	+1	84.2 kB
npm/[email protected]	None	0	0 B

View full report↗︎

[socket-security]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/[email protected]

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.02%. Comparing base (458c3fa) to head (912d073).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1198      +/-   ##
==========================================
- Coverage   74.02%   74.02%   -0.01%     
==========================================
  Files         182      182              
  Lines        4343     4342       -1     
  Branches     1064     1064              
==========================================
- Hits         3215     3214       -1     
  Misses       1128     1128              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[abretonc7s]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[christopherferreira9]

LGTM

[chakra-guy]

LGTM