mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
5a4d159846
## Summary Just change `dbConnect.js` to `dbConnect.ts` for correct path. ### Adding or Updating Examples - [x] The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md - [x] Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md <!-- Thanks for opening a PR! Your contribution is much appreciated. To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below. Choose the right checklist for the change(s) that you're making: ## For Contributors ### Improving Documentation - Run `pnpm prettier-fix` to fix formatting issues before opening the PR. - Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide ### Fixing a bug - Related issues linked using `fixes #number` - Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ### Adding a feature - Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas) - Related issues/discussions are linked using `fixes #number` - e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) - Documentation added - Telemetry added. In case of a feature if it's used or not. - Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md ## For Maintainers - Minimal description (aim for explaining to someone not on the team to understand the PR) - When linking to a Slack thread, you might want to share details of the conclusion - Link both the Linear (Fixes NEXT-xxx) and the GitHub issues - Add review comments if necessary to explain to the reviewer the logic behind a change ### What? ### Why? ### How? Closes NEXT- Fixes # --> Co-authored-by: JJ Kasper <jj@jjsweb.site>
50 lines
1.2 KiB
TypeScript
50 lines
1.2 KiB
TypeScript
import { getPayload } from "payload/dist/payload";
|
|
import config from "./payload.config";
|
|
|
|
if (!process.env.MONGODB_URI) {
|
|
throw new Error("MONGODB_URI environment variable is missing");
|
|
}
|
|
|
|
if (!process.env.PAYLOAD_SECRET) {
|
|
throw new Error("PAYLOAD_SECRET environment variable is missing");
|
|
}
|
|
|
|
/**
|
|
* Global is used here to maintain a cached connection across hot reloads
|
|
* in development. This prevents connections growing exponentially
|
|
* during API Route usage.
|
|
*
|
|
* Source: https://github.com/vercel/next.js/blob/canary/examples/with-mongodb-mongoose/lib/dbConnect.ts
|
|
*/
|
|
let cached = (global as any).payload;
|
|
|
|
if (!cached) {
|
|
cached = (global as any).payload = { client: null, promise: null };
|
|
}
|
|
|
|
export const getPayloadClient = async () => {
|
|
if (cached.client) {
|
|
return cached.client;
|
|
}
|
|
|
|
if (!cached.promise) {
|
|
cached.promise = await getPayload({
|
|
// Make sure that your environment variables are filled out accordingly
|
|
mongoURL: process.env.MONGODB_URI as string,
|
|
secret: process.env.PAYLOAD_SECRET as string,
|
|
config: config,
|
|
});
|
|
}
|
|
|
|
try {
|
|
cached.client = await cached.promise;
|
|
} catch (e) {
|
|
cached.promise = null;
|
|
throw e;
|
|
}
|
|
|
|
return cached.client;
|
|
};
|
|
|
|
export default getPayloadClient;
|