Bun uses yarn lock for it's binary file. Running the binary will produce the content of a yarn lock file (v1) Other option is to use the -y command on add and install. This will create a yarn lock file and then createLockFile can just modify the yarn.lock file instead? This is the PR made from #19113 and pushed due to #22402 being closed. PS Bun feels more stable since the PR was first created! This PR will resolve #22283 and start of #21075
47 lines
1.4 KiB
JavaScript
47 lines
1.4 KiB
JavaScript
const fs = require('fs');
|
|
|
|
function checkLockFiles() {
|
|
const errors = [];
|
|
if (fs.existsSync('package-lock.json')) {
|
|
errors.push(
|
|
'Invalid occurence of "package-lock.json" file. Please remove it and use only "pnpm-lock.yaml"'
|
|
);
|
|
}
|
|
if (fs.existsSync('bun.lockb')) {
|
|
errors.push(
|
|
'Invalid occurence of "bun.lockb" file. Please remove it and use only "pnpm-lock.yaml"'
|
|
);
|
|
}
|
|
if (fs.existsSync('yarn.lock')) {
|
|
errors.push(
|
|
'Invalid occurence of "yarn.lock" file. Please remove it and use only "pnpm-lock.yaml"'
|
|
);
|
|
}
|
|
try {
|
|
const content = fs.readFileSync('pnpm-lock.yaml', 'utf-8');
|
|
if (content.match(/localhost:487/)) {
|
|
errors.push(
|
|
'The "pnpm-lock.yaml" has reference to local repository ("localhost:4873"). Please use ensure you disable local registry before running "pnpm install"'
|
|
);
|
|
}
|
|
if (content.match(/resolution: \{tarball/)) {
|
|
errors.push(
|
|
'The "pnpm-lock.yaml" has reference to tarball package. Please use npm registry only'
|
|
);
|
|
}
|
|
} catch {
|
|
errors.push('The "pnpm-lock.yaml" does not exist or cannot be read');
|
|
}
|
|
return errors;
|
|
}
|
|
|
|
console.log('🔒🔒🔒 Validating lock files 🔒🔒🔒\n');
|
|
const invalid = checkLockFiles();
|
|
if (invalid.length > 0) {
|
|
invalid.forEach((e) => console.log(e));
|
|
process.exit(1);
|
|
} else {
|
|
console.log('Lock file is valid 👍');
|
|
process.exit(0);
|
|
}
|