
Product
Introducing Tier 1 Reachability: Precision CVE Triage for Enterprise Teams
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
@gnist/design-system
Advanced tools
@gnist/design-system
is a React component library containing reusable, multi-brand GUI building blocks for applications in the Møller ecosystem.
For instructions on developing components, see the Development docs.
The library is published as @gnist/design-system
in the public npm registry. The prefix @moller
is an npm scope associated with our organization on npm
Run the command
npm install @gnist/design-system @gnist/themes
To use the library, the vanilla-extract plugin needs to be used.
For Vite, you need
npm install -D @vanilla-extract/vite-plugin @vanilla-extract/esbuild-plugin
Your vite.config.ts
might look like this:
// vite.config.ts
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { vanillaExtractPlugin } from "@vanilla-extract/vite-plugin";
import { vanillaExtractPlugin as veEsbuildPlugin } from "@vanilla-extract/esbuild-plugin";
// https://vitejs.dev/config/
export default defineConfig({
plugins: [react(), vanillaExtractPlugin()],
optimizeDeps: {
esbuildOptions: {
// Handle vanilla-extract .css.js files during Vite dev mode optimization
// This prevents error "Styles were unable to be assigned to a file." in dev mode
// See https://github.com/vanilla-extract-css/vanilla-extract/discussions/1051
plugins: [veEsbuildPlugin({ runtime: true })],
},
},
});
In the application entrypoint, import the required global styles and choose a theme
// app.tsx
import { LocalizationProvider } from "@gnist/design-system";
// Import one or more of these themes
import { bilholdLight } from "@gnist/themes/themes/bilholdLight.css.js";
import { gumpen } from "@gnist/themes/themes/gumpen.css.js";
import { brandless } from "@gnist/themes/themes/brandless.css.js";
import { mollerBil } from "@gnist/themes/themes/mollerBil.css.js";
import { skoda } from "@gnist/themes/themes/skoda.css.js";
import { vw } from "@gnist/themes/themes/vw.css.js";
import { dahles } from "@gnist/themes/themes/dahles.css.js";
import { autoria } from "@gnist/themes/themes/autoria.css.js";
import { audi } from "@gnist/themes/themes/audi.css.js";
import { cupra } from "@gnist/themes/themes/cupra.css.js";
// Import global styles
import { globalTextStyles } from "@gnist/themes/typography.css";
// Import necessary fonts (one or more, dependent on which themes are in use)
import "@gnist/design-system/fonts/moller";
import "@gnist/design-system/fonts/bilhold";
import "@gnist/design-system/fonts/skoda";
import "@gnist/design-system/fonts/gumpen";
import "@gnist/design-system/fonts/VW";
import "@gnist/design-system/fonts/dahles";
import "@gnist/design-system/fonts/autoria";
import "@gnist/design-system/fonts/audi";
import "@gnist/design-system/fonts/cupra";
import "@gnist/design-system/fonts/tools";
// Apply the theme
document.body.classList.add(bilholdLight);
// Apply global styles
globalTextStyles.forEach((c) => {
document.body.classList.add(c);
});
export const App: React.FC = () => {
return (
<LocalizationProvider language="en">
{/* ...the rest of your app here...*/}
</LocalizationProvider>
);
};
If you are setting up in a Next.js project, the procedure is quite the same.
You will need to install and use @vanilla-extract/next-plugin
:
npm install -D @vanilla-extract/next-plugin
With this setup, your next.config.mjs
might look like this:
// next.config.mjs
import { createVanillaExtractPlugin } from "@vanilla-extract/next-plugin";
const withVanillaExtract = createVanillaExtractPlugin();
/** @type {import('next').NextConfig} */
const nextConfig = {};
export default withVanillaExtract(nextConfig);
If you are running a React version 18 project, you will also need to add this to your tsconfig.json
for it to work with this React 17 library.
// tsconfig.json
"paths": {
...
"react": [ "./node_modules/@types/react"]
}
Then add the styling to your layout.tsx
file. It might look like this:
// layout.tsx
import { bilholdLight } from "@gnist/themes/themes/bilholdLight.css.js";
import { globalTextStyles } from "@gnist/themes/typography.css.js";
import "@gnist/design-system/fonts/bilhold";
const bodyClassList = [bilholdLight, ...globalTextStyles];
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html lang="en">
<body className={bodyClassList.join(" ")}>{children}</body>
</html>
);
}
Finally, import components from @gnist/design-system
:
// index.tsx
import { PrimaryButton } from "@gnist/design-system";
export default function Home() {
return <PrimaryButton>Hello</PrimaryButton>;
}
If you are running Pages Router, add transpilePackages
to next.config.mjs
so that Vanilla Extract is applied to the library code:
// next.config.mjs
const nextConfig = {
transpilePackages: ["@gnist/design-system", "@gnist/themes"],
};
As Pages Router does not have layout.tsx
, you need to split the setup between
pages/_document.tsx
and pages/_app.tsx
.
_document.tsx
runs once on the server. Use a named import here to get the theme class for :
// _document.tsx
import { bilholdLight } from "@gnist/themes/themes/bilholdLight.css.js";
import { globalTextStyles } from "@gnist/themes/typography.css.js";
import "@gnist/design-system/fonts/bilhold";
const bodyClassList = [bilholdLight, ...globalTextStyles];
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html lang="en">
<body className={bodyClassList.join(" ")}>{children}</body>
</html>
);
}
_app.tsx
runs on every route change. Here you must use side-effect imports for the same theme and typography so the CSS actually ends up in the client bundle:
// _app.tsx
import { LocalizationProvider } from "@gnist/design-system";
// Fonts matching your chosen theme
import "@gnist/design-system/fonts/bilhold";
// Side-effect imports to include CSS/tokens in client bundle
import "@gnist/themes/themes/bilholdLight.css.js";
import "@gnist/themes/typography.css.js";
export default function MyApp({ Component, pageProps }: AppProps) {
return (
// Wrap app in LocalizationProvider
<LocalizationProvider language="en">
<Component {...pageProps} />
</LocalizationProvider>
);
}
This ensures:
_document.tsx
sets the correct theme class on and .
_app.tsx
loads the theme’s CSS variables and typography tokens into the client bundle.
@moller/design-system
If you are migrating from the old component library @moller/design.system
, please see the migration guide.
FAQs
Unknown package
The npm package @gnist/design-system receives a total of 325 weekly downloads. As such, @gnist/design-system popularity was classified as not popular.
We found that @gnist/design-system demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket’s new Tier 1 Reachability filters out up to 80% of irrelevant CVEs, so security teams can focus on the vulnerabilities that matter.
Research
/Security News
Ongoing npm supply chain attack spreads to DuckDB: multiple packages compromised with the same wallet-drainer malware.
Security News
The MCP Steering Committee has launched the official MCP Registry in preview, a central hub for discovering and publishing MCP servers.