[Snyk] Security upgrade node-sass from 4.14.1 to 9.0.0

[saumilmac]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• frontend/package.json
• frontend/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Inefficient Algorithmic Complexity SNYK-JS-BRACEEXPANSION-17706650	721

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

[saumilmac]

The upgrade from node-sass v4 to v9 is a major jump across several breaking versions. Most importantly, the node-sass package itself is deprecated and no longer receives feature updates. The official recommendation is to migrate to its successor, sass (Dart Sass).

Key Breaking Changes:

• Deprecation: node-sass and the underlying LibSass library are deprecated. They will not support new Sass or CSS features. The package's GitHub repository has been archived, and the npm package is marked as deprecated.
• Node.js Version Support: This is the most significant technical breaking change. node-sass versions are tightly coupled to specific Node.js versions. The target version 9.0.0 drops support for Node.js 14 and requires Node.js 16 or newer. The starting version 4.14.1 was compatible with Node.js 14.
• Security Default: Version 8.0.0 changed the default setting for rejectUnauthorized to true when fetching remote files, which may break builds that import from sources with invalid SSL certificates.

Recommendation:

Instead of upgrading node-sass, you should plan a migration to sass. This is a high-impact change that requires replacing the package entirely.

1. Uninstall node-sass: npm uninstall node-sass
2. Install sass: npm install --save-dev sass

While sass is designed as a replacement, you may need to update build scripts, as some command-line flags have changed (e.g., --output-style compressed becomes --style=compressed).

Source: GitHub Releases, Sass Blog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.