-
-
Notifications
You must be signed in to change notification settings - Fork 110
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: support package.yaml
#156
Conversation
@@ -49,7 +50,11 @@ async function readTarget(opts: { | |||
|
|||
if (GITHUB_WORKSPACE) { | |||
try { | |||
({ packageManager } = JSON.parse(readFileSync(path.join(GITHUB_WORKSPACE, packageJsonFile), 'utf8'))) | |||
const content = readFileSync(path.join(GITHUB_WORKSPACE, packageJsonFile), 'utf8'); |
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.
it is confusing that packageJsonFile can be a 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.
it is confusing that packageJsonFile can be a yaml
What do you suggest? @zkochan Rename all instances to packageFile
?
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.
We could rename the setting to package_file
or manifest_file
but the feature will be rarely used, so I don't think it is worth a breaking change
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 don't think it is worth a breaking change
Maybe just a note in the README then?
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.
See pnpm/pnpm#1100 and pnpm/pnpm#1799.