Skip to content
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

chore: update TypeScript to v5 #5271

Merged
merged 2 commits into from
May 14, 2024
Merged

chore: update TypeScript to v5 #5271

merged 2 commits into from
May 14, 2024

Conversation

aberonni
Copy link
Contributor

@aberonni aberonni commented May 9, 2024

AB#27996

Describe your changes

Updating TS to v5

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have added tests wherever relevant
  • I have made sure that all automated checks pass before requesting a review
  • I do not need any deviation from our PR guidelines

@aberonni aberonni force-pushed the aberonni/update-typescript branch from 124f777 to f3b3bd2 Compare May 9, 2024 08:49
@aberonni aberonni force-pushed the aberonni/update-typescript branch from f3b3bd2 to d1f662a Compare May 9, 2024 08:55
@aberonni aberonni force-pushed the aberonni/update-typescript branch from d1f662a to 248d172 Compare May 9, 2024 09:00
@aberonni aberonni force-pushed the aberonni/update-typescript branch 5 times, most recently from 24bee4b to 2483330 Compare May 9, 2024 10:35
@aberonni aberonni requested a review from elwinschmitz May 9, 2024 10:57
@aberonni aberonni marked this pull request as ready for review May 9, 2024 10:57
@aberonni aberonni changed the title Update TypeScript to v5 chore: update TypeScript to v5 May 9, 2024
@aberonni aberonni force-pushed the aberonni/update-typescript branch 4 times, most recently from 4b33dce to 0bfbe0e Compare May 10, 2024 13:44
@aberonni aberonni force-pushed the aberonni/update-typescript branch from 0c86744 to dc19f0b Compare May 14, 2024 13:40
@aberonni aberonni merged commit 15fffdf into main May 14, 2024
4 checks passed
@aberonni aberonni deleted the aberonni/update-typescript branch May 14, 2024 14:07
aberonni added a commit that referenced this pull request May 14, 2024
Merging the PR #5271 seems to have broken the service:
https://121-test.scm.azurewebsites.net/api/vfs/LogFiles/2024_05_14_ln0mdlwk00005A_default_docker.log

Error along the lines of (while starting the service):

```
npm start
2024-05-14T14:09:10.174478723Z npm info using npm@9.6.4
2024-05-14T14:09:10.174721026Z npm info using node@v18.19.1
2024-05-14T14:09:10.202707456Z
2024-05-14T14:09:10.202758857Z > start
2024-05-14T14:09:10.202765857Z > GLOBAL_121_VERSION=$(test -f "VERSION.txt" && cat VERSION.txt || echo $GLOBAL_121_VERSION)  node index.js
2024-05-14T14:09:10.202770557Z
2024-05-14T14:09:10.344822639Z node:internal/modules/cjs/loader:1137
2024-05-14T14:09:10.344871540Z   throw err;
2024-05-14T14:09:10.344877840Z   ^
2024-05-14T14:09:10.344882140Z
2024-05-14T14:09:10.344886340Z Error: Cannot find module 'typescript'
```

I think this should fix it. It still remains unclear to me how this happens in test, and we don't catch it sooner. One thing at a time :D
aberonni added a commit that referenced this pull request May 14, 2024
Merging the PR #5271 seems to have broken the service:
https://121-test.scm.azurewebsites.net/api/vfs/LogFiles/2024_05_14_ln0mdlwk00005A_default_docker.log

Error along the lines of (while starting the service):

```
npm start
2024-05-14T14:09:10.174478723Z npm info using npm@9.6.4
2024-05-14T14:09:10.174721026Z npm info using node@v18.19.1
2024-05-14T14:09:10.202707456Z
2024-05-14T14:09:10.202758857Z > start
2024-05-14T14:09:10.202765857Z > GLOBAL_121_VERSION=$(test -f "VERSION.txt" && cat VERSION.txt || echo $GLOBAL_121_VERSION)  node index.js
2024-05-14T14:09:10.202770557Z
2024-05-14T14:09:10.344822639Z node:internal/modules/cjs/loader:1137
2024-05-14T14:09:10.344871540Z   throw err;
2024-05-14T14:09:10.344877840Z   ^
2024-05-14T14:09:10.344882140Z
2024-05-14T14:09:10.344886340Z Error: Cannot find module 'typescript'
```

I think this should fix it. It still remains unclear to me how this happens in test, and we don't catch it sooner. One thing at a time :D
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants