---
name: inline-css
description: Efficiently manage CSS imports in TypeScript codebases, understanding tsc vs esbuild behavior for fast, low-config, maintainable setups.
title: inline-css
canonical_url: https://skilld.dev/gh/corey-alix/dwp-hours/inline-css
last_updated: 2026-10-07T01:30:59.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install corey-alix/dwp-hours/inline-css`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/inline-css`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/corey-alix/dwp-hours/inline-css) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/inline-css`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/inline-css --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/inline-css --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Agent Skill: Handling CSS Imports in TypeScript Projects (tsc vs esbuild)

**Skill Name**  
`css-imports-typescript-esbuild`

**Description**  
Efficiently manage `import "./styles.css"` (and `.module.css`) in TypeScript codebases.  
Understand what `tsc` does vs modern bundlers (especially **esbuild**).  
Prefer fast, low-config, maintainable setups.

**Applicable Versions** (as of Feb 2026)

- TypeScript ≥ 5.0
- esbuild ≥ 0.20 (behavior stable since ~0.8–0.12)

**Core Facts**

| Tool    | `import "./file.css"` allowed? | Inlines CSS into JS bundle?   | Emits separate `.css` file? | Default loader behavior                          | Best Use Case                          |
| ------- | ------------------------------ | ----------------------------- | --------------------------- | ------------------------------------------------ | -------------------------------------- |
| `tsc`   | Yes (with config)              | **Never**                     | No (ignores)                | No emit — only type checking                     | Pure type-checking + declaration emit  |
| esbuild | Yes                            | **Yes** — when `bundle: true` | Yes — when no JS entry      | `.css` → CSS → inject `<style>` or separate file | Most modern apps, libs, SSR front-ends |

**tsc — Type-Only Support (2025–2026 standard)**

Enable arbitrary non-JS imports without errors:

```jsonc
// tsconfig.json
{
  "compilerOptions": {
    "moduleResolution": "bundler",
    "module": "preserve", // or "esnext"
    "allowArbitraryExtensions": true,
    "noEmit": true, // common with esbuild/vite
    "isolatedModules": true,
  },
}
```

````

Optional — explicit module declaration for CSS Modules:

```ts
// src/styles.d.css.ts  (or global.d.ts)
declare module "*.css" {
  const classes: Record<string, string>;
  export default classes;
}

declare module "*.module.css" {
  const classes: Record<string, string>;
  export default classes;
}
```

→ `tsc` never emits CSS or JS code for it.
→ Use with esbuild / vite / rollup for actual bundling.

**esbuild — Recommended Default (fast & clean)**

Built-in CSS handling — no plugins needed in 99% of cases.

```js
// build.js (ESM)
import esbuild from "esbuild";

await esbuild.build({
  entryPoints: ["src/index.tsx"],
  bundle: true,
  minify: true,
  format: "esm",
  platform: "browser",
  outfile: "dist/app.js",
  // loader: { '.css': 'css' }          // default — usually not needed
  // or { '.module.css': 'local-css' }  // for CSS modules (exports object)
});
```

**Behavior Matrix (esbuild bundle: true)**

| Import style                            | Loader (default) | Result in browser bundle                    | Export value (if imported) |
| --------------------------------------- | ---------------- | ------------------------------------------- | -------------------------- |
| `import "./global.css"`                 | `css`            | Injects `<style>` tag at runtime            | `undefined` / void         |
| `import styles from "./mod.module.css"` | `local-css`      | Injects `<style>`, exports hashed class map | `{ [className]: string }`  |
| `import raw from "./file.css?raw"`      | `text` (manual)  | `raw` = string containing CSS               | `string`                   |

**Patterns – Pick One per Project**

1. **Browser SPA (Vite / esbuild dev + build)**
   → `import "./App.css"` → auto-injected styles
   → Use `local-css` for modules

2. **Library / Component (emits JS + separate CSS)**
   → `--bundle --splitting` + external CSS handling
   → Or emit CSS separately: `esbuild --entryPoints=src/index.ts src/index.css --outdir=dist`

3. **SSR / full inline (rare)**
   → Use plugin or custom loader → collect CSS strings
   → esbuild alone does **not** inline to JS string by default (unlike style-loader)

**Quick Checklist (Maintainable Setup)**

- [ ] `tsconfig.json`: `allowArbitraryExtensions`, `moduleResolution: "bundler"`
- [ ] Use esbuild (or Vite) — never rely on `tsc` for CSS emit
- [ ] Decide early: global CSS vs modules vs CSS-in-JS
- [ ] Avoid custom plugins unless you need PostCSS / Sass transforms
- [ ] Test: `import classes from "./Button.module.css"; classes.primary` → autocompletes & typesafe

**Verdict**
**tsc** → types only, no inlining, no emission
**esbuild** → inlines/injects CSS automatically when bundling → fastest path for most projects in 2026

Use this skill when: onboarding new TS+CSS repo, debugging "CSS not applying", choosing bundler.
````
