[
https://issues.apache.org/jira/browse/AIRAVATA-3650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604590#comment-17604590
]
ASF subversion and git services commented on AIRAVATA-3650:
-----------------------------------------------------------
Commit ba4cb0268f783f531849e98665038cd3b7b1c3b3 in airavata-django-portal's
branch
refs/heads/dependabot/npm_and_yarn/django_airavata/static/common/moment-2.29.4
from Marcus Christie
[ https://gitbox.apache.org/repos/asf?p=airavata-django-portal.git;h=ba4cb026 ]
AIRAVATA-3650 Switch from node-sass to dart-sass
> Switch from node-sass to dart-sass for sass compilation
> -------------------------------------------------------
>
> Key: AIRAVATA-3650
> URL: https://issues.apache.org/jira/browse/AIRAVATA-3650
> Project: Airavata
> Issue Type: Improvement
> Components: Django Portal
> Reporter: Marcus Christie
> Assignee: Marcus Christie
> Priority: Major
>
> There are a couple of issues with using node-sass:
> - [node-sass (and libsass which it depends on) is
> deprecated|https://sass-lang.com/blog/libsass-is-deprecated]
> - it is [very particular about what versions of node-sass work with what
> versions of
> Node|https://github.com/sass/node-sass#node-version-support-policy]. In the
> past, upgrades to the version of Node have broken the build because the newer
> version of Node didn't work with the version of node-sass we were using. See
> AIRAVATA-3536 for an example
> -- this has downstream affects too on Django apps
> Upgrading to the recommended dart-sass should fix both of these issues
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
