5 of 6 standards met
Describe the solution you'd like** Would be nice to add an optional package for an expo/react-native application. This would even be a nohoist package that is handled separately but can use the other packages for less code duplication. Edit: turns out this is not overly complex to add. from the root dir run: in under add in add in the new apps add under This was enough to get expo running in the same pnpm dev command with everything else. I still need to test it more extensively Edit 2.0 This breaks completely once you run from the root of the repo. It hoists dependencies and I cant seem to get beyond this point or revert the change
The tab headers in the component are not scaling properly when the window size changes. This issue affects the user experience, especially on smaller screens or when the window is resized. Steps to Reproduce: 1. Open the component in a browser. 2. Resize the window to a smaller width. 3. Observe that the tab headers do not scale properly and may overflow or become misaligned. Expected Behavior: The tab headers should scale appropriately with the window size, ensuring they remain visible and usable on all screen sizes. Current Behavior: The tab headers do not scale properly, leading to overflow or misalignment on smaller screens. Suggested Fix: Use responsive design techniques (e.g., CSS Flexbox, Grid, or media queries) to ensure the tab headers scale properly. Consider using a horizontal scroll for the tab headers if there are too many tabs to fit on smaller screens. Additional Context: The issue is observed in the component within . The tab headers are defined as follows: Labels: bug ui responsive-design
Repository: vercel/next-forge. Description: Production-grade Turborepo template for Next.js apps. Stars: 6906, Forks: 631. Primary language: TypeScript. Languages: TypeScript (91.8%), MDX (5.8%), CSS (1.6%), JavaScript (0.5%), HTML (0.1%). License: MIT. Homepage: https://www.next-forge.com/ Topics: betterstack, boilerplate, clerk, dark-mode, feature-flags, neon, nextjs, posthog, prisma, react, sentry, seo, stripe, tailwindcss, typescript. Latest release: v5.3.2 (2mo ago). Open PRs: 16, open issues: 44. Last activity: 1mo ago. Community health: 87%. Top contributors: haydenbleasel, dependabot[bot], davidmytton, jpvalery, julianbenegas, fmerian, yamz8, pedrocarlo, vercel[bot], anthonyshew and others.
TypeScript
Last 12 weeks Β· 2 commits
Describe the bug When expanding nested sections in the documentation sidebar (e.g., CMS, Packages, Addons), the footer at the bottom of the sidebar overlaps or behaves incorrectly. The layout appears visually broken when multiple dropdown sections are expanded. next-forge version Latest (please adjust if you know the exact version, e.g. vX.X.X) To Reproduce Steps to reproduce the behavior: 1. Go to the documentation site 2. Open the sidebar navigation 3. Expand sections such as CMS, Packages, or other nested groups 4. Observe the footer at the bottom of the sidebar Expected behavior The sidebar content should scroll correctly, and the footer should remain properly positioned without overlapping or breaking layout when dropdown sections are expanded. Screenshots If applicable, add screenshots to help explain your problem. Desktop (please complete the following information): OS: macOS Browser: Brave (Chromium-based)
Description The two supabase migration guide links in the callouts on the page were missing the prefix. Checklist [ ] My code follows the code style of this project. [ ] I have performed a self-review of my code. [ ] I have commented my code, particularly in hard-to-understand areas. [x] I have updated the documentation, if necessary. [ ] I have added tests that prove my fix is effective or my feature works. [ ] New and existing tests pass locally with my changes.