dididy opened a new pull request, #5068: URL: https://github.com/apache/zeppelin/pull/5068
### What is this PR for? Using a `.nvmrc` file allows people using `nvm` to easily specify and switch to the desired Node version. In my work, I often use different Node versions for Zeppelin and other projects, and switching between them every time can be cumbersome. Setting up a `.nvmrc` would automate this process, making it much more convenient. It would also allow `nvm` users to not worry about the Node version, thereby reducing unnecessary overhead. https://github.com/apache/superset/blob/master/docs/.nvmrc I looked at other Apache projects and found that Superset already uses a `.nvmrc` file. Therefore, it would be beneficial to apply the same to Zeppelin. And in this PR, I pinned Node to version **16.20.2** for both **zeppelin-web** and **zeppelin-web-angular**, the latest release of Node 16, using `.nvmrc`. ### What type of PR is it? Improvement ### Todos ### What is the Jira issue? * [[ZEPPELIN-6318](https://issues.apache.org/jira/browse/ZEPPELIN-6318)] ### How should this be tested? ### Screenshots (if appropriate) ### Questions: * Does the license files need to update? N * Is there breaking changes for older versions? N * Does this needs documentation? N -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: reviews-unsubscr...@zeppelin.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
