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 🙏

© 2024 – Pkg Stats / Ryan Hefner

bazik

v0.0.1

Published

Create a component library Vite.js tooling. Prettier code formatter.

Downloads

3

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

benjilegnardbenjilegnard

Keywords

Readme

Bazik ⚗️ an accessible library of rich components for Qwik ⚡️

This library aims to be accessible first.

And use Qwik's awesome performance to provide a good experience for everyone.

First goal is to implement most of the ARIA patterns : https://www.w3.org/WAI/ARIA/apg/patterns/

Components (roadmap)

  • Accordion
  • Alert
  • Dialog
  • Field
  • Select
  • Checkbox
  • DatePicker
  • Autocomplete
  • Breadcrumb
  • Button
  • Carousel
  • Combobox
  • Disclosure
  • Feed
  • Grid
  • Link
  • Listbox
  • Menu / Menubar
  • Menu Button
  • Meter
  • Radio Group
  • Slider
  • Multi-thumb slider
  • Spinbutton
  • Switch
  • Table
  • Tabs
  • Toolbar
  • Tooltip
  • TreeView
  • TreeGrid
  • Window splitter

Customization principles

Most of the customization should be done with css vars.

Development Builds

Client only

During development, the index.html is not a result of server-side rendering, but rather the Qwik app is built using client-side JavaScript only. This is ideal for development with Vite and its ability to reload modules quickly and on-demand. However, this mode is only for development and does not showcase "how" Qwik works since JavaScript is required to execute, and Vite imports many development modules for the app to work.

npm run dev

Server-side Rendering (SSR) and Client

Server-side rendered index.html, with client-side modules prefetched and loaded by the browser. This can be used to test out server-side rendered content during development, but will be slower than the client-only development builds.

npm run dev.ssr

Production Builds

A production build should generate the client and server modules by running both client and server build commands.

npm run build

Client Modules

Production build that creates only the client-side modules that are dynamically imported by the browser.

npm run build.client

Server Modules

Production build that creates the server-side render (SSR) module that is used by the server to render the HTML.

npm run build.ssr

Related