-
Notifications
You must be signed in to change notification settings - Fork 36
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
Node.js v18 Compatibility Test for [dashboards-search-relevance] #202
Comments
The official Node.js 18 PR raised in OSD: opensearch-project/OpenSearch-Dashboards#4071 |
opensearch-project/OpenSearch-Dashboards#4071 support node 14, 16 and 18. Pls test on node 18.
|
Cypress tests pass, sanity tests on local OSD instance pass. |
Can you please verify if this issue is related? Thanks! https://github.com/opensearch-project/dashboards-search-relevance/actions/runs/5085431385/jobs/9138888584?pr=205
|
|
Introduction
As part of our continued efforts to improve OpenSearch Dashboards, we are planning to upgrade the underlying Node.js version from v14 to v18. This change will enhance performance, add new features, and bolster security. However, such major version changes might also affect the compatibility of existing plugins. Here is more introduction: opensearch-project/OpenSearch-Dashboards#3601.
Therefore, we kindly request assistance in testing this plugin the compatibility of with this new version of Node.js. We've prepared a branch with the Node.js v18 upgrade, which you can find here:
https://github.com/AMoo-Miki/OpenSearch-Dashboards/tree/node-18-webpack-4
Steps to Proceed
The purpose of linking any questions or issues back to the main issue is to maintain visibility and transparency among all plugin owners. A problem encountered by one plugin might also affect others. This shared knowledge base will foster collaborative problem-solving and prevent duplication of effort.
We appreciate your support and cooperation in ensuring a smooth transition to Node.js v18 for the entire OpenSearch Dashboards community.
The text was updated successfully, but these errors were encountered: