Sonarlint latest version9/27/2023 ![]() It does not have any impact on the Node.js version targeted by your project code. The change applies specifically to the version of Node.js installed and used by the SonarCloud scanner analysis tool, either in your local build environment or in your cloud CI service. You should therefore move your Node.js environment to a supported version as soon as possible: ![]() This means that in August 2022, analysis of JS/TS/CSS will stop working in Node.js 12 environments.Support for Nodejs 12 will be deprecated on 15 March 2022 and end in August 2022.March 2022 - Deprecate support for Node.js 12 Please note that this change does not have any impact outside of your analysis runtime.įor more information on how payment and billing work, see Payments and Pricing. The recommended supported version is the latest LTS, which is currently Node.js 16.The minimum supported version will be Node.js 14.To continue to enjoy the latest rule updates, you should move your Node.js environment to a supported version as soon as possible: This will make the minimum supported version of Node.Js 14, but we recommend using the latest LTS version 16.You will no longer be able to create new projects within these environments. This means that starting today, analysis of JS/TS/CSS will stop working in Node.js 12 environments. ![]() This means that support will also be removed in the latest version of SonarLint. It has been considered EOL by OpenJS Foundation since March 2022 and has been deprecated since then. We would like to inform you that, as of September 15, 2022, the use of Node.js 12 will no longer be supported by analyses targeting SonarCloud. The minimum version requirement for this runtime will change soon: A Node.js runtime is required to run CI-based analysis of JavaScript, TypeScript or CSS. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |