OneDark-Pro VS node-sass

Now you are all set to start working on your project, but there are some more setting that you can change to make it even more suitable as per your need. You can change layout (I prefer the side bar on the right as it doesn't change the view when I open and close it). You can change color theme if you want to my personal favorite is Atom One Dark Pro.

It is OneDark with more vivid colors. E.g. compare the screenshots in the repo you linked to with Binaryify/OneDark-Pro, and you'll see the difference.

I write my code in Visual Studio Code with bunch of extensions (OneDark-Pro, Auto Rename Tag, Bracket Pair Colorizer, indent-rainbow, File Utils, to name a few), I use One Dark Pro Color Theme and Material Icon Theme.

Depends on what you mean by "use it". One Dark Pro uses it, but not extensively. I'd imagine the same is true for most themes - the feature is somewhat new and people are used to the TextMate syntax highlighting.

For many years, Culture Amp took the second option, and distributed shared components without compiled CSS. This meant that every app that consumed shared components needed to include the necessary CSS build tooling – at that time CSS Modules and node-sass – with a compatible version and configuration. This was relatively easy to set up, but over time proved difficult to maintain. When node-sass was deprecated in favour of (the much faster but slightly incompatible) Dart Sass, this demanded a difficult lock-step migration across all those codebases, which we have yet to achieve. And as new applications have switched to Tailwind for their own styles, they've had to continue to maintain those old build tools in parallel for the shared components' styles.

The project that we developed use a node version 14.18.0 and we use a node-sass version 4.14.1 package and this package also deprecated for today.

ES 2 component Sass files are compiled using dart Sass instead of node-sass. This change was made because node-sass has been deprecated.

node-sass - yes i am aware its deprecated 😅

C:\Webparts\react-script-editor>npm install npm WARN deprecated @types/[email protected]: This is a stub types definition. classnames provides its own type definitions, so you do not need this installed. > [email protected] install C:\Webparts\react-script-editor\node_modules\node-sass > node scripts/install.js Downloading binary from https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node Cannot download "https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node": HTTP error 404 Not Found

Are you referring to when it's trying to download 'https://github.com/sass/node-sass/releases/download/v4.12.0/win32-x64-83_binding.node' after I typed 'npm install'?

This Github issue helped me a lot.

remote: ERROR in ./app/javascript/stylesheets/application.scss (./node_modules/css-loader/dist/cjs.js??ref--7-1!./node_modules/postcss-loader/src??ref--7-2!./node_modules/sass-loader/dist/cjs.js??ref--7-3!./app/javascript/stylesheets/application.scss) remote: Module build failed (from ./node_modules/sass-loader/dist/cjs.js): remote: Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (93) remote: For more information on which environments are supported please see: remote: https://github.com/sass/node-sass/releases/tag/v4.14.1 remote: at module.exports (/tmp/build_37040035/node_modules/node-sass/lib/binding.js:13:13) remote: at Object. (/tmp/build_37040035/node_modules/node-sass/lib/index.js:14:35) remote: at Module._compile (node:internal/modules/cjs/loader:1101:14) remote: at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) remote: at Module.load (node:internal/modules/cjs/loader:981:32) remote: at Function.Module._load (node:internal/modules/cjs/loader:822:12) remote: at Module.require (node:internal/modules/cjs/loader:1005:19) remote: at require (node:internal/modules/cjs/helpers:102:18) remote: at getDefaultSassImpl (/tmp/build_37040035/node_modules/sass-loader/dist/index.js:198:10) remote: at Object.loader (/tmp/build_37040035/node_modules/sass-loader/dist/index.js:80:29)

Ah damn I did not save the full error before uninstalling everything and rethinking my next move. From the various posts it seems I'm not the only one having the same issue, but never really found out what the smartest solution would be to go forward as none of those suggestions worked with the latest node-js version.