feat: migrate project from node-sass to sass #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
node-sass package with sass (Dart Sass), ensuring better compatibility and future-proofing the project. The change also simplifies the build process by removing the need for native bindings, which often caused issues on newer systems like macOS with M1/M2 chips.
Key Changes:
Replaced node-sass with sass in package.json.
Updated the build and watch scripts to use sass instead of node-sass.
Removed the deprecated node-sass dependency, preventing potential installation issues.
Impact:
This update ensures smoother development and cross-platform compatibility without relying on deprecated packages. The project's build process is now faster and more reliable.