-
Notifications
You must be signed in to change notification settings - Fork 11
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 #306
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #306 +/- ##
=======================================
Coverage 77.62% 77.62%
=======================================
Files 34 34
Lines 648 648
Branches 162 162
=======================================
Hits 503 503
Misses 132 132
Partials 13 13 Continue to review full report in Codecov by Sentry.
|
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.
Left some clarifying questions about the changes, notably about the removal of @edx/frontend-platform
from the peerDependencies
.
@@ -60,7 +60,6 @@ | |||
"react-test-renderer": "16.14.0" | |||
}, | |||
"peerDependencies": { | |||
"@edx/frontend-platform": "^1.9.6 || ^2.0.0", |
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.
[clarification] Why are we removing this peer dependency? @edx/frontend-platform
is used by the catalog-search
package and is up to the MFE (consumer) to install, not this package. This is why @edx/frontend-platform
is a devDependency
, not a dependency
.
It should denote the full range of versions of @edx/frontend-platform
that catalog-search
is compatible with. If one of these existing versions is removed from the existing peer dependency list, this package needs to be released as a breaking change.
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.
Yes, this package is expected to be released as a breaking change
@@ -11,6 +11,7 @@ import { SearchField } from '@edx/paragon'; | |||
import debounce from 'lodash.debounce'; | |||
import { connectSearchBox } from 'react-instantsearch-dom'; | |||
|
|||
// eslint-disable-next-line import/no-extraneous-dependencies |
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 can likely be removed once @edx/frontend-platform
is added back as a peer dependency.
packages/hotjar/package.json
Outdated
@@ -38,7 +38,8 @@ | |||
"sideEffects": false, | |||
"devDependencies": { | |||
"@edx/browserslist-config": "1.1.0", | |||
"@edx/frontend-build": "12.3.0", | |||
"@edx/frontend-build": "12.7.0", | |||
"@edx/frontend-platform": "4.0.1", |
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.
[clarification] Why is @edx/frontend-platform
installed in hotjar
when hotjar
doesn't use it? Keep in mind this repo is a monorepo and each package within the monorepo has a unique set of dependencies.
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.
Yes, that was my bad as these were updated through a script
@@ -1,5 +1,6 @@ | |||
import PropTypes from 'prop-types'; | |||
import { useParams } from 'react-router-dom'; | |||
// eslint-disable-next-line import/no-extraneous-dependencies |
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 will likely go away once @edx/frontend-platform
is added back as a peer dependency.
packages/utils/src/analytics.js
Outdated
@@ -1,3 +1,4 @@ | |||
// eslint-disable-next-line import/no-extraneous-dependencies |
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 will likely go away once @edx/frontend-platform
is added back as a peer dependency.
packages/utils/src/hooks.js
Outdated
@@ -1,4 +1,5 @@ | |||
import { useRef, useEffect, useState } from 'react'; | |||
// eslint-disable-next-line import/no-extraneous-dependencies |
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 will likely go away once @edx/frontend-platform
is added back as a peer dependency.
@BilalQamar95 Also, keep in mind... we still have not straightened out the Lerna release/publish config for this repository since Axim (FKA tCRIL) required the |
Hi all, is there anyway we could fix the CLA bot issue and get this merged? It's blocking some of the work on FC-0012 project which is sparked by the Translation Infrastructure update OEP-58. Please let me or @brian-smith-tcril know if there's anything we can do to unblock this PR. |
… into bilalqamar95/node-v18-upgrade
@adamstankiewicz could please review it again and merge it |
Hello all! This would help to fix a GoCD pipeline failure happening in |
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, assuming the updated packages are released as a breaking change, i.e. new major verison.
Thanks all!! This is very helpful! |
Ticket
Upgrade Node Js from 16 to 18
Description
Merge checklist:
frontend-app-learner-portal-enterprise
,frontend-app-admin-portal
, andfrontend-app-enterprise-public-catalog
). Will consumers safely be able to upgrade to this change without any breaking changes?BREAKING CHANGE
so the NPM package is released as such.Post merge:
chore(release): publish
) that incremented versions in relevant package.json and CHANGELOG files, and created Git tags for those versions.Publish from package.json
Github Action workflow to publish these new package versions to NPM.master
branch.npm view <package_name> versions --json
).