[GH-ISSUE #1051] Bump on #1049 #621

New issue

Closed

opened 2026-02-26 02:33:43 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 02:33:43 +03:00

Owner

Originally created by @handhikadj on GitHub (Aug 19, 2019).
Original GitHub issue: https://github.com/koel/koel/issues/1051

@phanan You should have not closed an issue before it's confirmed to resolved.

Same step when installing but now i've checkout v3.7.2 and using "node-sass": "^4.9.4" and still get that error.

have been trying the workarounds on these issues:
#748, #732, and trying this issue: https://github.com/sass/node-sass/issues/1764
still got that error

anyway, by checkout-ing / breaking this package down into releases and bad-written docs, this package is broken.
why don't you put it into master like another production-ready app?

Node version: v8.16.1
NPM version: v6.4.1
Yarn version: v1.17.3

Originally created by @handhikadj on GitHub (Aug 19, 2019). Original GitHub issue: https://github.com/koel/koel/issues/1051 @phanan You should have not closed an issue before it's confirmed to resolved. Same step when installing but now i've checkout v3.7.2 and using `"node-sass": "^4.9.4"` and still get that error. have been trying the workarounds on these issues: #748, #732, and trying this issue: https://github.com/sass/node-sass/issues/1764 still got that error anyway, by `checkout`-ing / breaking this package down into releases and bad-written docs, this package is broken. why don't you put it into master like another production-ready app? Node version: v8.16.1 NPM version: v6.4.1 Yarn version: v1.17.3

kerem closed this issue

2026-02-26 02:33:43 +03:00

kerem commented

2026-02-26 02:33:44 +03:00

Author

Owner

@phanan commented on GitHub (Aug 19, 2019):

I personally never had the problem, which lies in node-sass apparently and not in Koel, that's why I pointed you to the relevant issue which you can use as a start for to solve the problem.

anyway, by checkout-ing / breaking this package down into releases and bad-written docs, this package is broken.
why don't you put it into master like another production-ready app?

This makes no sense, sorry.

@phanan commented on GitHub (Aug 19, 2019): I personally never had the problem, which lies in `node-sass` apparently and not in Koel, that's why I pointed you to the relevant issue which you can use as a start for to solve the problem. > anyway, by checkout-ing / breaking this package down into releases and bad-written docs, this package is broken. > why don't you put it into master like another production-ready app? This makes no sense, sorry.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/koel-koel#621

No description provided.

Rows
Columns