Skip to content

fix: configure throws when package.json is missing #2063

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 7, 2024
Merged

fix: configure throws when package.json is missing #2063

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions scripts/configure.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -649,6 +649,12 @@ export function configure(params, fs = nodefs) {

writeAllFiles(files, packagePath).then(() => {
const packageManifest = path.join(packagePath, "package.json");
if (!fs.existsSync(packageManifest)) {
// We cannot assume that the app itself is an npm package. Some libraries
// have an 'example' folder inside the package.
return;
}

const newPackageManifest = updatePackageManifest(packageManifest, config);
fs.writeFile(
packageManifest,
Expand Down