-
Notifications
You must be signed in to change notification settings - Fork 54
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
fix: use es2021 as a target for TypeScript #900
Conversation
test/resolver/resolver.spec.ts
Outdated
expect(error.cause).to.be.an('error'); | ||
expect(error.cause).to.have.property('message').that.equals('custom'); |
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.
Let's keep the assertion and add the cause
back somehow.
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.
Should I just provide that es2022 TS code here then? As a kind of TS polyfill?
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, restoring cause
as a custom property in ResolutionError
is a good option.
test/resolver/resolver.spec.ts
Outdated
expect(error.cause).to.be.an('error'); | ||
expect(error.cause).to.have.property('message').that.equals('custom'); |
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, restoring cause
as a custom property in ResolutionError
is a good option.
* fix: use es2021 as a target for TypeScript * fix: get rid of es2022 code * fix: restore error.cause --------- Co-authored-by: Anton Platonov <[email protected]>
Fixes #897