-
Notifications
You must be signed in to change notification settings - Fork 7
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
Update dependencies and fix Yarn 2 enable bug #140
Conversation
1f5816f
to
3515f05
Compare
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 would put the Yarn 2 uplift related changes into a different commit .
@@ -42,7 +42,7 @@ suite('Unit Test: Metadata Parser', () => { | |||
const testAndExpectCode = async (filename: string, code: string) => { | |||
await assert.rejects( | |||
() => parseMetadata(path.join(staticPath, filename)), | |||
(err) => { | |||
(err: MetadataParseError) => { |
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.
Shouldn't you use the MetadataParseError in the next test case too?
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.
This change was just to silence a TS type-error because it couldn't deduce the error type of parseMetadata.
Might as well use the type on the next case as well, fixed.
* A recent change requires that Corepack is enabled on the system if we want to interact with Yarn 1 at all, even if that is just to enable Yarn 2+.
3515f05
to
eef200f
Compare
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.
LGTM
Updates yarn to 4.1.0, dependencies to latest available, fixes nodejs update-related issues, and fix enabling Yarn Stable in CI.