npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@fortanix/baklava

v1.0.0-beta-20251209

Published

Fortanix Baklava design system

Downloads

561

Readme

npm CI

Fortanix Baklava Design System

This repository contains the Baklava design system used to build Fortanix products.

You can find the latest Storybook documentation here.

Usage

Requirements:

  • React v19 or higher.

Installation:

npm install --save @fortanix/baklava

Add the BaklavaProvider to the top level of your application, in order to enable certain features like toast notifications:

import { BaklavaProvider } from '@fortanix/baklava';

export const App = () => {
  <BaklavaProvider>
    <MyApp/>
  </BaklavaProvider>
};

To import a component:

import { Button } from '@fortanix/baklava';

For the styling, add the following import to your main CSS file:

@use '@fortanix/baklava';

Icons are loaded through SVG sprites. This requires some additional setup. If you're using vite, install the vite-plugin-svg-icons-ng plugin:

npm install --save vite-plugin-svg-icons-ng

Then, add the following to the plugins array in your vite config:

import { createSvgIconsPlugin } from 'vite-plugin-svg-icons-ng';

export default {
  plugins: [
    createSvgIconsPlugin({
      iconDirs: [path.resolve(__dirname, 'node_modules/@fortanix/baklava/src/assets/icons')],
      symbolId: 'baklava-icon-[name]',
      inject: 'body-last',
      customDomId: 'baklava-icon-sprite',
    }),
  ],
};

Additionally, you will need to add the following import in your main entry file:

import 'virtual:svg-icons/register';

Please make sure that Baklava is the first CSS that gets loaded in to your bundle. Baklava relies on CSS cascade layers for its specificity management. If your application emits any code that uses an @layer name that is also used by Baklava (like baklava.components), and Baklava's layer ordering is not emitted first, then the ordering of the layers will get messed up (since browsers order layers by source order). If you want, you can also just emit the layers ordering from Baklava explicitly (rather than the whole bundle):

@use '@fortanix/baklava/styling/layers.scss';
@include layers.styles;

Contributing

We gratefully accept bug reports and contributions from the community. By participating in this community, you agree to abide by Code of Conduct. All contributions are covered under the Developer's Certificate of Origin (DCO).

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.

License

This project is primarily distributed under the terms of the Mozilla Public License (MPL) 2.0, see LICENSE for details.