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.
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
feat: no lockfiles in tarballs by default #1385
Conversation
src/commands/pack/tarballs.ts
Outdated
@@ -9,6 +9,7 @@ Add a pretarball script to your package.json if you need to run any scripts befo | |||
|
|||
static flags = { | |||
parallel: Flags.boolean({description: 'Build tarballs in parallel.'}), | |||
'preserve-lockfiles': Flags.boolean({description: 'Preserve lockfiles in the tarball.'}), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the argument for this being an opt-out flag? As opposed to an opt-in flag like --remove-lockfiles
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
default to what most people probably want? That's what we said when we talked.
Could go either way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think my preference is to make it an opt-in flag so that we don't risk suddenly breaking other people's builds - even if it's a small risk.
I have a list of of things to do in the next major. If we want, we can switch to an opt-out flag then
} | ||
} | ||
|
||
const isLockFile = (f: string) => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pnpm-lock.yaml
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, didn't know about that one, will add.
* fix: compile after install and tests * test: set git config before cli integration tests * test: skip pack tests for pnpm
pack:tarballs
gets a new--prune-lockfiles
flag.This is done after
addDependencies
so that the lockfiles affect that step.forcedotcom/cli#2835