mongodb-starter
A developer directory built on Next.js and MongoDB Atlas, deployed on Vercel with the Vercel + MongoDB integration.
by vercelTypeScript
Commit activity
Last 12 weeks · 0 commits
Community health
1 of 6 standards met
37
✓README○License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 2 in progress · Last activity 2y ago
See all on GitHub →
from looking at the history of the mongodb connection handling code, it started out with pretty much the code from the with-mongodb example however it eventually ended up with caching the connection in global in both dev and production (even though there is a comment in the example about not using the global for production, which i don't understand why tbh). is there a reason for that / an issue that made you switch the way of handling the connection? also could you share the peak number of opened database connections you had and if possible what was the traffic like then? as i am wondering how the number of connections scales with traffic
TL;DR: The should not be updated to Next 13, while the entire project is built with Next 12. For anyone who wants to deploy this project: Use next 12.1.6 all the time, just like the lock file suggests. If you just clone the main branch and do you will get Link tag error For Vercel team: I suggest you to archive this project or fix More information: I notice that gazdagergo and hkbertoson created PR to fix Link tag error, and I tried your fix but the error still exists. Regards,
Hello. I'm new to TypeScript, and still new to programming in general. Forgive me if the answer is obvious, but how do I enable searching? Or is it already enabled and I just have to tweak some things? Thanks in advance :) Please feel free to DM me.
Recent fixes
renders at the top of the error page. The phrase has two problems: 1. is misspelled 2. The canonical HTTP 500 status name is , not Replacing the whole phrase with the correct status name () is the right fix.
Ran to update to the latest Link config. Also removed from next.config.js as it was throwing an error stating it was not supported.
Migrate MongoDB Codebase to PostgreSQL using Prisma Summary This pull request migrates the existing MongoDB codebase to PostgreSQL using Prisma. The migration includes setting up a Neon Postgres instance, creating a corresponding database schema with relations, and updating the codebase to interact with PostgreSQL instead of MongoDB. Changes Initialized Prisma in the project and created the file with initial models for and . Created a Neon Postgres database using and set the connection URI in the file. Replaced MongoDB-specific code in with Prisma client setup for PostgreSQL. Updated the file to use Prisma for database seeding, aligning the fields with the Prisma schema. Applied Prisma migrations to create the necessary tables in the PostgreSQL database. Installed the PostgreSQL adapter for NextAuth.js and removed MongoDB dependencies. Testing Ran the seeding script to populate the PostgreSQL database with initial data. Verified successful execution of the seeding script without errors. Ensured that the updated codebase interacts correctly with the PostgreSQL database. Next Steps Review the changes and provide feedback. Merge the branch into the main branch after approval. Monitor the application for any issues related to the database migration. Link to Devin run: https://preview.devin.ai/devin/a78e1739f5c6440084ea33c7992d1c3a This Devin run was requested by Nikita.
Structured data for AI agents
Repository: vercel/mongodb-starter. Description: A developer directory built on Next.js and MongoDB Atlas, deployed on Vercel with the Vercel + MongoDB integration. Stars: 510, Forks: 156. Primary language: TypeScript. Languages: TypeScript (94.4%), JavaScript (3.9%), CSS (1.6%). Homepage: https://mongodb.vercel.app Open PRs: 2, open issues: 10. Last activity: 2y ago. Community health: 37%. Top contributors: steven-tey, leerob, gt-codes, chriswdmr, smaeda-ks, agrittiwari, 3mdistal, ggallon.