@nordicsemiconductor/pc-nrfconnect-shared 242.0.0 → 244.0.0

package/Changelog.md

@@ -7,6 +7,27 @@ This project does _not_ adhere to
 [Semantic Versioning](https://semver.org/spec/v2.0.0.html) but contrary to it
 every new version is a new major version.
 
+## 244.0.0 - 2026-01-22
+
+### Changed
+
+- Major upgrade of `esbuild` and `esbuild-sass-plugin` which brings along Sass
+  updates and deprecations.
+
+## 243.0.0 - 2026-01-22
+
+### Fixed
+
+- shared@232 introduced a bug that the `NRFUTIL_*` env variables were not
+  cleared which could cause problems if users set them in their environment.
+
+### Changed
+
+- Added an ESLint error if the module 'process' is imported. This is usually not
+  needed (because it is available as the global `process`) and might cause
+  problems (if it is imported as `process` it may hinder replacing NODE_ENV
+  during compilation).
+
 ## 242.0.0 - 2026-01-20
 
 ### Added

package/README.md

@@ -17,6 +17,16 @@ If there is no latest entry there yet, and you do not intend to release the
 change as a new version right ahead, add a new section with the heading
 `## Unreleased` at the top.
 
+## Disabled Sass warnings
+
+Because we still use an outdated version of Bootstrap, we would get several Sass
+warnings when using the latest version of Sass. Our goal is to move away from
+Bootstrap (and mostly also plain CSS/Sass) but until that is accomplished we
+would get those warnings. Because of that, some Sass warnings are silenced. If
+you want to see all Sass warnings, set the env variable
+`ENABLE_ALL_SASS_WARNINGS` to `true` while building an app or shared, e.g. by
+calling `ENABLE_ALL_SASS_WARNINGS=true npm run build:dev`.
+
 ## Releasing
 
 To release, two files must be up-to-date:

package/config/eslintrc.js

@@ -82,6 +82,19 @@ module.exports = {
         ],
         'no-console': 'off',
         'no-param-reassign': 'off',
+        'no-restricted-imports': [
+            'error',
+            {
+                name: 'process',
+                message:
+                    'Do not import process, it is available as a global `process` and importing it may cause issues with replacing NODE_ENV.',
+            },
+            {
+                name: 'node:process',
+                message:
+                    'Do not import node:process, it is available as a global `process` and importing it may cause issues with replacing NODE_ENV.',
+            },
+        ],
         'no-shadow': 'off',
         'no-undef': 'error',
         'no-unused-expressions': 'off',