-
Notifications
You must be signed in to change notification settings - Fork 1
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
build: updates ts-node version (#2757) #1394
Conversation
✅ Deploy Preview for detroit-public-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for detroit-partners-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for detroit-storybook-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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.
looks good, just a console log
@@ -457,7 +457,7 @@ describe("Applications", () => { | |||
await supertest(app.getHttpServer()) | |||
.get(`/applications/${createRes.body.id}`) | |||
.set(...setAuthorization(user1AccessToken)) | |||
.expect(404) | |||
.expect(500) |
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.
Just curious why this changed here
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 also done in core, and we should look into why this changed there. I'll create an issue off of this.
Co-authored-by: Yazeed Loonat <YazeedLoonat@gmail.com>
This brings over a fix from core which updates the ts-node version