securityos/node_modules/next/dist/esm/lib/find-config.js

44 lines
1.6 KiB
JavaScript

import findUp from "next/dist/compiled/find-up";
import fs from "fs";
import JSON5 from "next/dist/compiled/json5";
export function findConfigPath(dir, key) {
// If we didn't find the configuration in `package.json`, we should look for
// known filenames.
return findUp([
`.${key}rc.json`,
`${key}.config.json`,
`.${key}rc.js`,
`${key}.config.js`,
`${key}.config.cjs`
], {
cwd: dir
});
}
// We'll allow configuration to be typed, but we force everything provided to
// become optional. We do not perform any schema validation. We should maybe
// force all the types to be `unknown` as well.
export async function findConfig(directory, key, _returnFile) {
// `package.json` configuration always wins. Let's check that first.
const packageJsonPath = await findUp("package.json", {
cwd: directory
});
if (packageJsonPath) {
const packageJson = require(packageJsonPath);
if (packageJson[key] != null && typeof packageJson[key] === "object") {
return packageJson[key];
}
}
const filePath = await findConfigPath(directory, key);
if (filePath) {
if (filePath.endsWith(".js") || filePath.endsWith(".cjs")) {
return require(filePath);
}
// We load JSON contents with JSON5 to allow users to comment in their
// configuration file. This pattern was popularized by TypeScript.
const fileContents = fs.readFileSync(filePath, "utf8");
return JSON5.parse(fileContents);
}
return null;
}
//# sourceMappingURL=find-config.js.map