Fabulous Las Vegas

A VS Code color theme inspired by the iconic Welcome to Fabulous Las Vegas Nevada sign — in day and night editions.

Themes

Fabulous Las Vegas — High Noon (light)
Fabulous Las Vegas — After Dark (dark)

Preview

Fabulous Las Vegas — After Dark (dark)

Fabulous Las Vegas — After Dark

Fabulous Las Vegas — High Noon (light)

Fabulous Las Vegas — High Noon

Installation

Open VS Code
Go to Extensions (Ctrl+Shift+X)
Search for Fabulous Las Vegas
Click Install
Open the Command Palette (Ctrl+Shift+P) and select Preferences: Color Theme
Choose Fabulous Las Vegas — High Noon or Fabulous Las Vegas — After Dark

From source

git clone https://github.com/alpharomercoma/fabulous-las-vegas-extension ~/.vscode/extensions/fabulous-las-vegas

Restart VS Code and select the theme from Preferences: Color Theme.

Color Palette

Color	Role	Day	Night
Roulette Red	Keywords, tags	`#C9122B`	`#F0455D`
Fabulous Blue	Functions	`#00769B`	`#0090BE`
Vegas Teal	Types, classes	`#0C7566`	`#0E9783`
Fremont Gold	Strings	`#946800`	`#B17C00`
Sunset Orange	Numbers	`#A04500`	`#DD5F00`
Flamingo Pink	Constants, decorators	`#B5325E`	`#D45D85`
Rat Pack Sand	Comments	`#7D6D5E`	`#958372`
Desert Earth	Foreground	`#352A1D`	`#E8DDD0`
Fremont Neon	UI accents	`#FCBA05`	`#FCBA05`

All syntax colors meet WCAG AA contrast requirements (minimum 4.5:1).

Publishing (CI)

Publishing to the Visual Studio Marketplace and the Open VSX Registry is automated with GitHub Actions. The extension is packaged once, then published to both registries in parallel.

Setup

Visual Studio Marketplace — Create a Personal Access Token (Azure DevOps / marketplace) with Marketplace (Publish) scope. Add a repo secret: VS_MARKETPLACE_TOKEN.
Open VSX Registry — Create an Eclipse account, link GitHub, sign the Publisher Agreement, then create an access token. Create the namespace once (replace alpharomercoma and <token>):
```
npx ovsx create-namespace -p alpharomercoma <token>
```
Add a repo secret: OPEN_VSX_TOKEN.
In the repo: Settings → Secrets and variables → Actions and ensure both VS_MARKETPLACE_TOKEN and OPEN_VSX_TOKEN are set.

How to release

Option A — Bump version and publish: Actions → Bump Version → Run workflow, choose patch / minor / major. The workflow bumps package.json, pushes the commit, creates a tag (e.g. v0.1.2), and Release & Publish Extension runs and publishes to both marketplaces in parallel.
Option B — Publish an existing version: Create a GitHub Release with a tag like v0.1.2 (or push a tag: git tag v0.1.2 && git push origin v0.1.2). Release & Publish Extension sets package.json version from the tag and publishes to both registries.

Author

Alpha Romer Coma — alpharomercoma@proton.me

License

MIT