Move to sass

[hkollmann]

see #10146.
I found a way to trick out the sass loading problem.
This should solve all node-sass problems.

Should be backportet to compiler

[cboulanger]

This is excellent, thank you very much!

[johnspackman]

Does this solve the compatibility problem with jsdom?

[hkollmann]

Does this solve the compatibility problem with jsdom?

Not in generally. It solves the problem loading sass in qooxdoo compiler. We do not use jsdom there - we use outr own generated windows problem.

You can use this approach to load sass with jsdom. I have'nt tried it it.
The idea is to trick out sass:

process.versions.electron = "0.0.0"; Tells sass that we are in a node enviroment
window.document.currentScript = {src: ""}; Prevents sass to access to the document.scripts variable

[oetiker]

sass seems quite a bit slower ... but then again, I guess we do not have a performance problem there, or do we?
https://www.peterbe.com/plog/quick-comparison-between-sass-and-node-sass

[hkollmann]

sass seems quite a bit slower ... but then again, I guess we do not have a performance problem there, or do we?
https://www.peterbe.com/plog/quick-comparison-between-sass-and-node-sass

No we do not have a performance problem.
We do have the problem that node-sass

• is deprecated: https://www.npmjs.com/package/node-sass
• we have npm install problems because there do not exists precompiled node-sass versions for each platfom and node version