Skip to content

docs(skill): reset-css needs no plugin configuration #668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
owjs3901 merged 1 commit into from
Sep 15, 2026
Merged

docs(skill): reset-css needs no plugin configuration #668

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 22 additions & 5 deletions SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -480,15 +480,32 @@ package you do not author**, such as an offline webfont package.

### `@devup-ui/reset-css`

It is a package, so the plugin has to be told to process it or its classes are
never emitted. With Vite the two resolver settings are needed as well:
Install it and import it. **It needs no plugin configuration**, on any bundler:

```tsx
// app/layout.tsx
import { resetCss } from "@devup-ui/reset-css";

resetCss();
```

```ts
plugins: [DevupUI({ include: ["@devup-ui/reset-css"] })],
optimizeDeps: { exclude: ["@devup-ui/reset-css"] },
ssr: { noExternal: ["@devup-ui/reset-css"] },
// vite.config.ts - nothing extra
plugins: [DevupUI()];
```

The reset is a `globalCss()` call at the top level of the package's own module,
and `resetCss()` is an empty function that exists only so the import is not
tree-shaken away. So the one thing that has to happen is that the plugin
transforms the package inside `node_modules` — and every plugin already allows
`@devup-ui` and `@devup-editor` through that exclusion unconditionally, with
`include` only *adding* to that list. `ssr.noExternal` is set from a `/@devup-ui/`
pattern for the same reason.

Do not add `include`, `optimizeDeps.exclude` or `ssr.noExternal` entries for it.
They are redundant, and writing them suggests to the next reader that a devup-ui
package needs wiring when none does.

## What Decides Static Extraction

One rule explains `Dynamic Values = CSS Variables`, `$token Scope` and
Expand Down
Loading