Dark Autumn Frost Theme

VSCode dark theme with autumn colors and a little bit of frost (inspired by the Coffee Dark Roast theme). You can help by reporting issues here

Screenshot

Getting started

The easiest way to install is for free from the Visual Studio Code Marketplace

Activate theme

Launch Quick Open,

• Linux Ctrl + Shift + P
• macOS ⌘ + Shift + P
• Windows Ctrl + Shift + P

Type theme and choose Preferences: Color Theme, then select Dark Autumn Frost.

Other Ways to Install

From Quick Open

Launch Quick Open

• Linux Ctrl+P
• macOS ⌘P
• Windows Ctrl+P

Paste the following command and press Enter:

ext install dark-autumn-frost

Packaged VSIX Extension

Download the latest .vsix release file from the marketplace and install it from the command line

code --install-extension dark-autumn-frost-*.*.*.vsix

or from within VS Code by launching Quick Open and running the Install from VSIX... command.

GitHub Repository Clone

Change to your .vscode/extensions VS Code extensions directory. Depending on your platform it is located in the following folders:

• Linux ~/.vscode/extensions
• macOs ~/.vscode/extensions
• Windows %USERPROFILE%\.vscode\extensions

Clone the Dark Autumn Frost Theme repository as fimius.dark-autumn-frost:

git clone https://github.com/fimius23/dark-autumn-frost.git fimius.dark-autumn-frost

Notes For Development

The project is structured to have all the colors defined in src/settings.js and the Theme file themes/theme.json to be built using the command gulp build. Any editing of scopes should happen in src/theme.json.

Prerequisites

• node/npm
• gulp

Commands

• gulp build builds the source file into the themes/ directory
• gulp clean removes the source file and themes/ directory
• npm run prepublish will prepare the source files and put them into the compiled themes/ directory, to be consumed by NPM

Tagging

Preparing the Tag

This project uses standard-version to prepare CHANGELOG.md and tag the project.

Run the command:

npm run release

Then verify that your CHANGELOG.md and your package.json look correct. As long as your git commit messages are conventional and accurate, you no longer need to specify the semver type - and you get CHANGELOG generation for free!

Commiting Your Changes

Run the command:

git push --follow-tags origin master