Updated node_config package to 3.3 to fix the deprecation warnings #1346
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes following deprecation warnings:
Upgraded playwright version as well, because pipeline is failing with this error:
This suggested to upgrade to fix the issue.
What has been done to verify that this works as intended?
All tests are passing, application is running correctly in local.
Why is this the best possible solution? Were any other approaches considered?
NA
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Package is used by a lot of endpoints, but usage is trivial so smoke test of the application should be enough. It is also okay to ship this in the next release.
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
None
Before submitting this PR, please make sure you have:
make test
and confirmed all checks still pass OR confirm CircleCI build passes