You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Indeed, node-sass is the main stumbling block when trying to update to a new version.
The main development flow currently is to use a docker container.
I'm suspecting this is needed for the deployment? As v14 is not supported anymore by GitHub Actions?
But this shouldn't take too long, I'm estimating two hours, I can take a look at this and upgrade node-sass. I've done it before for other repos.
It is mainly an inconvenience for newcomers, and I assume we are also
missing out on features and security improvements introduced in later node
versions
On Tue, 25 Jul 2023, 12:43 David Britt, ***@***.***> wrote:
Indeed, node-sass is the main stumbling block when trying to update to a
new version.
The main development flow currently is to use a docker container.
I'm suspecting this is needed for the deployment? As v14 is not supported
anymore by GitHub Actions?
But this shouldn't take too long, I'm estimating two hours, I can take a
look at this and upgrade node-sass. I've done it before for other repos.
—
Reply to this email directly, view it on GitHub
<#199 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAITTH2YLOKKBXVPEMDUARTXR6PMJANCNFSM6AAAAAA2WT472Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
At the moment only NodeJS 14 can be used to run this project, as we are relying on
node-sass
(?)I'm not an expert is the NodeJS ecosystem, could you comment @djmbritt on what is needed to support newer node versions?
The text was updated successfully, but these errors were encountered: