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

@meaningfuldata/soil

v0.7.15

Published

Soil components and libraries

Downloads

12

Readme

Soil

WIP: this project is still at an early stage of development.

Features

Conventions

Folder per component domain

All the related code is aggregated:

  • Components
  • External services
  • Types
  • Constants
  • Unit tests
  • Storybook stories
  • Fixtures (used on unit tests and Storybook stories)
  • Mocks

Components are defined and used with their entire namespace (SComponent), although they are stored without it (domain/SComponent).

Folder per layout

Similar to components, layouts should include all the children components that exist only to support them. Only the layout component should be exported. That main component could be named _.vue to keep the folder as the name (in layouts/MyLayout/_.vue the name is LayoutMyName).

CSS modules

Vue SFC should use CSS modules when possible. There are 2 special settings:

  • It is possible to use ._ as class name. It is replaced by the component name. It is useful for the root element.
  • It is possible to use camelCase in the template (.myClass) while using kebab-case on the CSS (my-class).

Setup

yarn add @meaningfuldata/soil

Dependencies

yarn add @fortawesome/vue-fontawesome @fortawesome/fontawesome-svg-core axios lodash-es vue-i18n

Scripts

Compile and serve the application for development

yarn serve

Compile and minify for production

yarn build

Run unit tests

yarn test:unit

Watch and run unit tests on changes

yarn test:unit:watch

Debug unit tests

yarn test:unit:inspect

Run end-to-end tests

yarn test:e2e

Watch and run end-to-end tests on changes

yarn test:e2e:watch

Lint and fix code

yarn lint

Serve the storybook

yarn storybook

Build the storybook

yarn storybook:build

License

Apache 2.0

Authors