nojsui
v1.0.0
Published
Copy NojsUI components into your project (shadcn-style). The only JS artifact in NojsUI, and it is optional.
Maintainers
Readme
nojsui
The CLI for NojsUI. It copies component source into your project shadcn-style — you own the files afterwards.
This is the only JavaScript NojsUI ships, and it is entirely optional: the
components are plain .css and .html files you can also copy by hand from
@nojsui/core.
Usage
npx nojsui list # what the kit has
npx nojsui add popover # copy popover into ./nojsui/add writes:
nojsui/
tokens.css only if it is not already there
base.css only if it is not already there
popover/
popover.css
popover.htmlThen link the three stylesheets in that order and paste the markup. You own the files from that point on — there is no config file, no lockstep and nothing to migrate.
Options
| Option | Default | What it does |
| --- | --- | --- |
| --dir <path> | nojsui | Where to write, relative to where you run it. |
| --force | off | Overwrite existing component files. Without it, an add that would overwrite anything writes nothing and exits 1. |
| -h, --help | | Usage. |
| -v, --version | | The version, which is also the @nojsui/core version it copies from. |
tokens.css and base.css are never overwritten, with or without --force —
they are yours to edit, and a second add must not undo that.
Where the files come from
The CLI copies from @nojsui/core, its single dependency, pinned to the exact
version the CLI ships with. Nothing is fetched at runtime, so nojsui add
works offline and always installs the components that were tested with that
release. See ADR 0025.
Links
- Docs and live demos: https://nojsui.com
MIT © SekiUI
