@thelabnyc/typed-scss-modules


Generate TypeScript definitions (.d.ts) files for CSS Modules that are written in SCSS (.scss). Check out this post to learn more about the rationale and inspiration behind this package.

!Example

For example, given the following SCSS:

``scss
@import "variables";

.text {
color: $blue;

&-highlighted {
color: $yellow;
}
}
`

The following type definitions will be generated:

`ts
export declare const text: string;
export declare const textHighlighted: string;
`

Basic Usage

Install & use:

`sh
npm install --save-dev @thelabnyc/typed-scss-modules
npx typed-scss-modules src
`

Or:

`sh
npx @thelabnyc/typed-scss-modules
`

CLI Options

For all possible commands, run typed-scss-modules --help.

The only required argument is the directory where all SCSS files are located. Running typed-scss-modules src will search for all files matching src/*/.scss. This can be overridden by providing a glob pattern instead of a directory. For example, typed-scss-modules src/*.scss

$3

- Type: boolean
- Default: false
- Example: typed-scss-modules src --watch

Watch for files that get added or are changed and generate the corresponding type definitions.

$3

- Type: boolean
- Default: false
- Example: typed-scss-modules src --watch --ignoreInitial

Skips the initial build when passing the watch flag. Use this when running concurrently with another watch, but the initial build should happen first. You would run without watch first, then start off the concurrent runs after.

$3

- Type: string[]
- Default: []
- Example: typed-scss-modules src --watch --ignore "**/secret.scss"

A pattern or an array of glob patterns to exclude files that match and avoid generating type definitions.

$3

- Type: string[]
- Default: []
- Example: typed-scss-modules src --includePaths src/core

An array of paths to look in to attempt to resolve your @import declarations. This example will search the src/core directory when resolving imports.

$3

- Type: object
- Default: {}
- Example: typed-scss-modules src --aliases.~some-alias src/core/variables

An object of aliases to map to their corresponding paths. This example will replace any @import '~alias' with @import 'src/core/variables'.

$3

- Type: object
- Default: {}
- Example: typed-scss-modules src --aliasPrefixes.~ node_modules/

An object of prefix strings to replace with their corresponding paths. This example will replace any @import '~bootstrap/lib/bootstrap' with @import 'node_modules/bootstrap/lib/bootstrap'.
This matches the common use-case for importing scss files from node_modules when sass-loader will be used with webpack to compile the project.

$3

- Type: "all" | "camel" | "kebab" | "param" | "snake" | "dashes" | "none"
- Default: "camel"
- Examples:
- typed-scss-modules src --nameFormat camel
- typed-scss-modules src --nameFormat kebab --nameFormat dashes --exportType default. In order to use multiple formatters, you must use --exportType default.

The class naming format to use when converting the classes to type definitions.

- all: makes use of all formatters (except all and none) and converts all class names to their respective formats, with no duplication. In order to use this option, you must use --exportType default.
- camel: convert all class names to camel-case, e.g. App-Logo => appLogo.
- kebab/param: convert all class names to kebab/param case, e.g. App-Logo => app-logo (all lower case with '-' separators).
- dashes: only convert class names containing dashes to camel-case, leave others alone, e.g. App => App, App-Logo => appLogo. Matches the webpack css-loader camelCase 'dashesOnly' option.
- snake: convert all class names to lower case with underscores between words.
- none: do not modify the given class names (you should use --exportType default when using --nameFormat none as any classes with a - in them are invalid as normal variable names).
Note: If you are using create-react-app v2.x and have NOT ejected, --nameFormat none --exportType default matches the class names that are generated in CRA's webpack's config.

$3

- Type: boolean
- Default: false
- Example: typed-scss-modules src --listDifferent

List any type definition files that are different than those that would be generated. If any are different, exit with a status code 1.

$3

- Type: "named" | "default"
- Default: "named"
- Example: typed-scss-modules src --exportType default

The export type to use when generating type definitions.

#### named

Given the following SCSS:

`scss
.text {
color: blue;

&-highlighted {
color: yellow;
}
}
`

The following type definitions will be generated:

`typescript
export declare const text: string;
export declare const textHighlighted: string;
`

#### default

Given the following SCSS:

`scss
.text {
color: blue;

&-highlighted {
color: yellow;
}
}
`

The following type definitions will be generated:

`typescript
export type Styles = {
text: string;
textHighlighted: string;
};

export type ClassNames = keyof Styles;

declare const styles: Styles;

export default styles;
`

This export type is useful when using kebab (param) cased class names since variables with a - are not valid variables and will produce invalid types or when a class name is a TypeScript keyword (eg: while or delete). Additionally, the Styles and ClassNames types are exported which can be useful for properly typing variables, functions, etc. when working with dynamic class names.

$3

- Type: string
- Default: "ClassNames"
- Example: typed-scss-modules src --exportType default --exportTypeName ClassesType

Customize the type name exported in the generated file when --exportType is set to "default".
Only default exports are affected by this command. This example will change the export type line to:

`typescript
export type ClassesType = keyof Styles;
`

$3

- Type: string
- Default: "Styles"
- Example: typed-scss-modules src --exportType default --exportTypeInterface IStyles

Customize the interface name exported in the generated file when --exportType is set to "default".
Only default exports are affected by this command. This example will change the export interface line to:

`typescript
export type IStyles = {
// ...
};
`

$3

- Type: "single" | "double"
- Default: "single"
- Example: typed-scss-modules src --exportType default --quoteType double

Specify a quote type to match your TypeScript configuration. Only default exports are affected by this command. This example will wrap class names with double quotes ("). If Prettier is installed and configured in the project, it will be used and is likely to override the effect of this setting.

$3

- Type: boolean
- Default: false
- Example: typed-scss-modules src --updateStaleOnly

Overwrite generated files only if the source file has more recent changes. This can be useful if you want to avoid extraneous file updates, which can cause watcher processes to trigger unnecessarily (e.g. tsc --watch). This is done by first checking if the generated file was modified more recently than the source file, and secondly by comparing the existing file contents to the generated file contents.

Caveat: If a generated type definition file is updated manually, it won't be re-generated until the corresponding scss file is also updated.

$3

- Type: "verbose" | "error" | "info" | "silent"
- Default: "verbose"
- Example: typed-scss-modules src --logLevel error

Sets verbosity level of console output.

#### verbose

Print all messages

#### error

Print only errors

#### info

Print only some messages

#### silent

Print nothing

$3

- Type: string
- Default: undefined
- Example: typed-scss-modules src --banner '// This is an example banner\n'

Will prepend a string to the top of your output files

`typescript
// This is an example banner
export type Styles = {
// ...
};
`

$3

- Type: string
- Default: _none_
- Example: typed-scss-modules src --outputFolder __generated__

Set a relative folder to output the generated type definitions. Instead of writing the type definitions directly next to each SCSS module (sibling file), it will write to the output folder with the same path.

It will use the relative path to the SCSS module from where this tool is executed. This same path (including any directories) will be constructed in the output folder. This is important for this to work properly with TypeScript.

Important: for this to work as expected the tsconfig.json needs to have rootDirs added with the same output folder. This will allow TypeScript to pick up these type definitions and map them to the actual SCSS modules.

`json
{
"compilerOptions": {
"rootDirs": [".", "__generated__"]
}
}
`

$3

- Type: string
- Default: _none_
- Example: typed-scss-modules src --additionalData '$global-var: green;'

Prepend the provided SCSS code before each file. This is useful for injecting globals into every file, such as adding an import to load global variables for each file.

$3

- Type: boolean
- Default: false
- Example: typed-scss-modules src --allowArbitraryExtensions

Output filenames that will be compatible with the "arbitrary file extensions" feature that was introduced in TypeScript 5.0. See the docs for more info.

In essence, the .scss.d.ts extension now becomes .d.scss.ts so that you can import SCSS modules in projects using ESM module resolution.

Config options

All options above are also supported as a configuration file in the root of the project. The following configuration file names are supported:

- typed-scss-modules.config.ts
- typed-scss-modules.config.js

The file can provide either a named config export or a default export.

`js
// Example of a named export with some of the options sets.
export const config = {
banner: "// customer banner",
exportType: "default",
exportTypeName: "TheClasses",
logLevel: "error",
};

// Example of a default export with some of the options sets.
export default {
banner: "// customer banner",
exportType: "default",
exportTypeName: "TheClasses",
logLevel: "error",
};
`

> Note: the configuration options are the same as the CLI options without the leading dashes (--). Only the full option name is supported (not aliases) in the configuration file.

CLI options will take precedence over configuration file options.

In addition to all CLI options, the following are options only available with the configuration file:

$3

- Type: AnyImporter[]
- Default: _none_

Define an array of custom SASS importers. This should only be necessary if custom SASS importers are already being used in the build process. This is used internally to implement aliases and aliasPrefixes.

Refer to lib/sass/importer.ts for more details and the Sass importer documentation.

Examples

For examples of how this tool can be used and configured, see the examples` directory:

- Basic example
- Default export example
- Config file (with custom importers) example
- Output folder example