-
Notifications
You must be signed in to change notification settings - Fork 32
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: upgraded to node v18, added .nvmrc and updated workflows #977
Changes from 29 commits
6aa6fed
372e6dd
6203d67
a66b322
12fb6a7
80b867d
c8c1537
15eb05d
ebc18a7
7f7be04
ae8397e
91a9495
74df5e1
85898a9
482b527
b3972c8
9745b31
1c60555
1c63db1
2a96d0b
ca478ef
59a6a50
2f9920f
5a40e60
45f4605
f55730b
4541b8b
d450b09
d4b7325
8250251
e627265
6a6c2f3
e05fd4f
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
16 | ||
18.15 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would recommend setting this as just the major version There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You are correct, but in this particular case I pinned it because of "TypeError: Cannot redefine property: window" issue. It was a bug fixed by nodejs/node#46615 but it wasn't back-ported to v18.16 at the time when I made these commits thus causing the aforementioned error, to resolve the issue I pinned it to v18.15. It seems that is has since been back-ported and the issue is now resolved. I have updated the version in |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,4 +3,6 @@ const { getBaseConfig } = require('@edx/frontend-build'); | |
|
||
const config = getBaseConfig('babel'); | ||
|
||
config.presets.push('@babel/preset-typescript'); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [clarification] Is this addition necessary given See tl;dr; I believe general TypeScript configs like this one should live in the default configs provided by There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, you are right. I ran into |
||
|
||
module.exports = config; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [suggestion] It looks like There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thank you for your suggestion, we agree that the current |
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 if the
node-version-file
attribute was considered when constructing the workflow. We could retain the original strategy matrix attributes, but point directly to the.nvmrc
file as a reference to the intended node version to upgrade to.Docs: https://github.com/actions/setup-node/blob/main/docs/advanced-usage.md#node-version-file
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.
The workflow was created by arbi-bom originally and with node v18 upgrades it spread across all the remaining MFEs where it was not being used previously. I'm not sure if
node-version-file
was considered while constructing it but I could see the merit to retain the original strategy matrix attributes. We can explore this further, thanks for bringing it to our attention.