Skip to content
| Marketplace
Sign in
Visual Studio Code>Programming Languages>Sass/SCSS Parameter CompletionNew to Visual Studio Code? Get it now.
Sass/SCSS Parameter Completion

Sass/SCSS Parameter Completion

boomba286

| (0) | Free
Completes Sass function and mixin parameter names in SCSS, Sass, and Vue files.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

Sass/SCSS Parameter Completion

CI Visual Studio Code Node.js Dart Sass License: MIT

Autocomplete parameter names for Sass functions and mixins in the .scss and .sass files of any project — React, Angular, Vue, or plain HTML.

Parameters you have already passed by name are never suggested twice, and preceding positional arguments are taken into account. Built-in Sass modules (sass:math, sass:color, …) are supported out of the box, and so are the functions, mixins, and variables you @use from your own files.

@function rem($value, $base: 16) {
  @return math.div($value, $base) * 1rem;
}

.card {
  /* typing `$` after the positional argument suggests `$base` */
  width: rem(12, $);
}

Features

Your own functions, mixins, and variables

  • Suggests parameter names when you type $, a comma, or just after an opening parenthesis.
  • Works for the @function and @mixin definitions in your project, called by bare name or through a @used module.
  • After a @used module's namespace. completes its functions and mixins, and after namespace.$ completes its variables, resolved from the file the @use points at.
  • Skips named parameters already used in the current call and accounts for preceding positional arguments.
  • Indexes @function, @mixin, and $variable declarations from the SCSS and Sass files in the workspace.

Built-in Sass modules

  • Recognizes namespaces loaded with @use 'sass:<module>' (including as <alias>).
  • Completes parameters for built-in functions and mixins, marking each as required, optional (with default), or rest.
  • Completes built-in module members after namespace. and built-in variables after namespace.$ (for example math.$pi).
  • Provides the same support for the seven built-in modules: math, string, color, list, map, selector, and meta.

Namespace and @use completion

  • In @use 'sass:… completes built-in module ids together with a short description.
  • Completes the names of namespaces already loaded with @use.

Hover documentation

  • Hovering a built-in function or mixin shows its signature, per-parameter descriptions (required/optional/default), a usage example, and a link to the official documentation.
  • Hovering a built-in variable shows its description and documentation link.
  • Hovering a workspace module member shows its signature.

Diagnostics

  • Underlines built-in module calls that are missing required arguments.
  • Underlines uses of undefined $variables.

Supported Languages

Language Extensions Completion Hover Diagnostics
SCSS .scss Yes Yes Yes
Indented Sass .sass Yes Yes Yes
Vue .vue Yes Yes —

Framework Support

The extension works on the .scss and .sass files in a project, independent of the framework. Any framework that keeps its styles in real Sass files is covered.

Framework How Sass is used Support
React / Next.js import styles from './Button.module.scss' (CSS Modules), or global .scss Yes — completes inside the .scss files
Angular styleUrls: ['./button.component.scss'], or standalone component style files Yes — completes inside component .scss files
Vue <style lang="scss"> in an SFC, or standalone .scss files Yes — completes inside .vue and .scss files
Plain HTML / others Standalone .scss / .sass files Yes

Styles that are not backed by a Sass document are not covered, because there is no SCSS text to complete in:

  • CSS-in-JS template literals (for example styled-components or emotion).
  • Angular inline styles: ['...'] string literals.

Configuration

Setting Type Default Description
sass-scss-completion.exclude string[] [] Additional glob patterns excluded from workspace indexing, on top of the built-in list (dependency, build output, and cache directories). Each entry must be a single pattern, for example vendor-legacy or **/generated/**.

Example:

{
  "sass-scss-completion.exclude": ["vendor-legacy", "**/generated/**"]
}

The workspace index is rebuilt automatically when files change and whenever this setting changes.

Usage

1. Parameters of your own functions and mixins

Define a function or mixin anywhere in the workspace, then call it — by bare name after @use, or through the module namespace. Typing $ (or a comma) suggests the parameters that are still unfilled.

/* _definitions.scss */
@function rem($value, $base: 16) {
  @return $value;
}

@mixin box($width, $height: 10) {
  width: $width;
  height: $height;
}

/* usage.scss */
@use 'definitions';

.usage {
  /* typing `$` suggests `$base` (the positional `12` fills `$value`) */
  width: rem(12, $);
}

.card {
  /* typing `$` suggests `$height` (the positional `100px` fills `$width`) */
  @include definitions.box(100px, $);
}

A parameter already passed by name is not suggested again.

.card {
  /* `$height` is already used, so only `$width` remains */
  @include definitions.box($height: 10px, $);
}

2. Members and variables of an imported module

After a @used module's namespace, its functions and mixins are suggested; after namespace.$, its variables are suggested.

/* _tokens.scss */
$spacing: 8px;

@function scale($factor, $base: 16) {
  @return $factor * $base;
}

@mixin flex-center($gap: 0) {
  display: flex;
  gap: $gap;
}

/* usage.scss */
@use 'tokens';

.grid {
  /* after `tokens.` suggests `scale` and `flex-center` */
  padding: tokens.scale(2, 8px);
}

.grid {
  /* after `tokens.$` suggests `$spacing` */
  margin: tokens.$spacing;
}

3. Built-in module function parameters

@use 'sass:color';

.button {
  /* typing `$` here suggests the remaining channel parameters */
  color: color.adjust(#036, $lightness: 20%);
}

Hovering color.adjust shows its parameters, an example, and a documentation link.

4. Built-in module members and variables

After the namespace dot, members of the module are suggested:

@use 'sass:math';

.grid {
  /* after `math.` suggests `div`, `ceil`, `floor`, `percentage`, … */
  width: math.div(10px, 2);
}

After $, the module's variables are suggested:

@use 'sass:math';

.circle {
  /* after `math.$` suggests `$e`, `$pi`, `$max-number`, … */
  circumference: 2 * math.$pi;
}

5. @use module paths

/* typing inside the quotes suggests built-in modules with descriptions */
@use 'sass:ma';

6. Loaded namespaces

Namespaces loaded with @use are completed by prefix:

@use 'sass:color';
@use 'tokens' as t;

.alert {
  /* typing `co` suggests the `color` namespace */
  color: co;
}

7. Diagnostics

@use 'sass:math';

.a {
  /* error: Missing required argument(s) $number2 in the call to math.div. */
  width: math.div(12);
}

.b {
  /* error: Used undefined variable $undefined. */
  height: $undefined;
}

Installation

From the Marketplace: search for Sass/SCSS Parameter Completion and install it.

From a VSIX package: package the extension and install it through Install from VSIX in the Extensions view:

npx @vscode/vsce package

Development

Requirements: Node.js 20 or later and VS Code 1.75 or later (or a compatible editor such as Trae).

npm install
npm run build

Press F5 to launch the Extension Development Host, then open an SCSS or Sass file in that host and try a function or mixin call.

Tests

Core logic (Vitest):

npm test

End-to-end against a real VS Code host:

npm run test:e2e

The E2E run uses a locally installed VS Code by default. Set VSCODE_EXECUTABLE_PATH to point at a different executable. On a headless machine, download a VS Code build by unsetting that variable, or run it under a virtual display such as xvfb-run -a.

Releasing

Publishing uses GitHub Actions Trusted Publishing (OIDC); no VSCE_PAT secret is required. In GitHub repository settings, create a marketplace environment and require a reviewer before deployment. In the Visual Studio Marketplace publisher settings, create a Trusted Publishing policy with these values:

  • Provider: GitHub Actions
  • Repository owner: boomba286
  • Repository: sass-scss-completion
  • Workflow: release.yml
  • Environment: marketplace

The release job requests an OIDC token and publishes the packaged VSIX. Keep id-token: write on the job and the --oidc option on the vsce publish command. Add a repository ruleset for v* tags that restricts tag creation to release maintainers. The workflow also rejects a release tag unless its commit is already reachable from main.

  1. Update version in package.json and add a matching entry to CHANGELOG.md.
  2. Commit and merge the change into main.
  3. Push a tag matching the version, and the Release workflow builds, runs the unit and E2E tests, packages the extension, and publishes it:
git tag v0.1.0
git push origin v0.1.0

The workflow fails if the tag and the package.json version differ.

Known Limitations

  • Workspace functions and mixins are indexed by name across the workspace; module visibility is not fully resolved.
  • If multiple definitions share a name, the first definition found is used.
  • Only definitions in .scss and .sass files are indexed.
  • Workspace variables are completed through namespace.$; a bare $variable name outside a call is not completed.
  • Missing-required-argument diagnostics apply to built-in module calls whose namespace is declared with @use 'sass:<module>'.

License

MIT. See LICENSE.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft