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

svemantic

v0.0.4

Published

Now tuned to Fomantic-UI 2.9.2

Downloads

5

Readme

Svemantic

Now tuned to Fomantic-UI 2.9.2

Alpha mode: you don' t see me

Library documentation entrance

Installation

Fomantic-UI needs some installation steps. The configuration is provided so that semantic generates in svelte-kit's static/dist folder that can be git-ignored.

TL;DR

$ cd node_modules/fomantic-ui
$ npx gulp install
$ cd semantic/
$ npx gulp build

What it does and does not

What it does

  • Implements elements by allowing reactive attributes to specific components to interract directly with the classes.
  • Implements Semantic-UI jQuery calls with arguments given by reactive attributes
  • Makes events or even promises out of call backs
  • Automate and re-order some content managements (like Tabs, Grids)
  • Centralize internationalization
  • Completely typed with typescript

What it does not

  • Implements each and every nuance of Semantic-UI. Some are let to simple class specifications
<div class="ui vertical divider">
and
</div>

Implemented

  • [x] Button
  • [ ] Container
  • ~~Divider~~
  • Emoji
  • [x] Flag
  • [ ] Header
  • [x] Icon
  • [ ] Image
  • [x] Input
  • [x] Label
  • [ ] List
  • [x] Loader
  • Placeholder
  • Rail
  • Reveal
  • Segment
  • [ ] Step
  • Text

Collections

  • [ ] Breadcrumb
  • [X] Form
  • [x] Grid
  • [x] Menu
  • [ ] Message
  • [x] Table

Views

  • [ ] Advertisement
  • [ ] Card
  • [ ] Comment
  • [ ] Feed
  • [ ] Item
  • [ ] Statistic

Modules

  • [x] Accordion
  • [ ] Calendar
  • [x] Checkbox
  • [x] Dimmer
  • [x] Dropdown
  • [ ] Embed
  • [ ] Flyout
  • [x] Modal
  • [ ] Nag
  • [x] Popup
  • [ ] Progress
  • [ ] Rating
  • [ ] Search
  • [ ] Shape
  • [ ] Sidebar
  • [ ] Slider
  • [ ] Sticky
  • [x] Tab (refactored)
  • [x] Toast
  • [ ] Transition

How to...

Developing

Once you've created a project and installed dependencies with npm install (or pnpm install or yarn), start a development server:

npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open

Everything inside src/lib is part of your library, everything inside src/routes can be used as a showcase or preview app.

Building

To build your library:

npm run package

To create a production version of your showcase app:

npm run build

You can preview the production build with npm run preview.

To deploy your app, you may need to install an adapter for your target environment.

Publishing

Go into the package.json and give your package the desired name through the "name" option. Also consider adding a "license" field and point it to a LICENSE file which you can create from a template (one popular option is the MIT license).

To publish your library to npm:

npm publish