These notes are pretty much the same steps as the two extensions list, it's just that I had to collate them together because neither seems to list it fully in the proper order.
-
Install Synthwave ’84/Synthwave + Fluoromachine theme on VS Code (I used the Fluoromachine one)
-
Install Custom CSS and JS Loader
-
Command + Shift + P to open command palette > "Preferences: Open settings (JSON)"
-
Add to the settings object this key, and the value is an array containing the path to the CSS file for your extension. On a Mac it should be the following:
{
"vscode_custom_css.imports": [
"file:///Users/${username}/.vscode/extensions/${extension folder name}/${extensions css file name}.css"
]
}
So for Synthwave + Fluoromachine on my Mac it's:
{
"vscode_custom_css.imports": [
"file:///Users/katesmac/.vscode/extensions/webrender.synthwave-x-fluoromachine-0.0.9/synthwave-x-fluoromachine.css"
]
}
- Quit VS Code and go to terminal so we can restart it with proper Permissions
- Type
sudo chown -R $(whoami) PATH TO CODE
where PATH TO CODE is actually the file path, and you actually type${whoami}
as well
So I typed exactly:
sudo chown -R $(whoami) /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Electron
- the back slashes in front of the space are important
6a. According to Custom CSS and JS Loader, if you are using 'Insiders Branch' then the VS Code file path might be: /Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron
but idk what that means
-
Should prompt you for your password
-
Reopen VS Code
-
Command + Shift + P > "Reload Custom CSS and JS"
-
Restart VS Code one more time and hopefully you'll see the glow!
- SPECIAL NOTE: If Code complains about that it is corrupted, simply click “Don't show again”.
- NOTE: Every time after Code is updated, please re-enable Custom CSS.
- NOTE: Every time you change the configuration, please re-enable Custom CSS.
Alright WIP "coming soon" (read before "Winds of Winter"): VS Code without the super user warnings, without the corruption notice, in fact, without any of the restrictions that necessitated all this jumping through hoops as the superuser in the first place just to get a little CSS working. To be fair they have to be worried about xss attacks etc in some environments that code is running but my machine is not one of them, yeah maybe in theory it could happen on my machine, but the simple fact is I do not care one iota if it does, cause I can always go download all my data back out of the cloud, MS as a professional shop cant take that attitude. [One of the few advantages of being unemployed: the luxury of not having to worry about the customers, unfortunately it is far outweighed by the the downside that the customers do in fact pay all of the bills so I can't say I recommend it]