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

livia-components

v0.3.2

Published

[![CircleCI](https://circleci.com/gh/holding-digital/livia-components.svg?style=svg&circle-token=a6ffde338e27b8391a728c9ef19d5759826e2040)](https://circleci.com/gh/holding-digital/livia-components) [![Codacy Badge](https://api.codacy.com/project/badge/Gra

Downloads

23

Readme

Livia Components

CircleCI Codacy Badge

Dependencies

  • Node.js >= v9;

Starting the project

  • Clone this repository: git clone [email protected]:holding-digital/livia-components.git;
  • Install all dependencies: npm install (or npm i);
  • Run npm run dev (or npm run start) for development environment http://localhost:3000
  • Run npm run start:proxy for use proxy and access the microservices http://localhost:4000/api/:microservice
  • Run npm run build for production

Patterns

Stylus > CSS

Stylus Doc

Stylus is “pythonic” (i.e. indentation-based). Whitespace is significant, so we substitute { and } with an indent, and an outdent as shown below:

.class-name
  color: $color-name

Structure

├── stylus
│   ├── areas
│   │   ├── *.styl
│   ├── general
│   │   ├── *.styl
│   ├── mixins
│   │   ├── *.styl
│   ├── thirdparty
│   │   ├── *.styl
└── main.styl

Colors

Obs: For declaration of color variables, you must always use hexadecimal, in caps lock and do not use abbreviations.

Example:

`$`color-name = `#FFFFFF`
`$`color-name-surname = `#000000`

Fonts

Sizes

  $font-hero = 36px
  $font-primary = 26px
  $font-second = 22px
  $font-subhead = 18px
  $font-body = 16px

B.E.M Methodology

http://getbem.com/naming/

Tests

  • This project uses the Jest test framework to run tests and make assertions. This library makes writing tests as easy as speaking - you describe a unit of your code and expect it to do the correct thing.

  • We use this glob pattern to find unit tests /**/*.spec.js - this tells Jest to run all files that end with .spec.js anywhere within the app folder. Use this to your advantage, and put unit tests next to the files you want to test so relevant files stay together!

Running tests

  • Run npm run test

Create new test

  • Sprinkle .spec.js files directly next to the parts of your application you want to test. (Or in __test__/ subdirectories, it doesn't really matter as long as they are directly next to those parts and end in .spec.js)

  • Write your unit and component tests in those files. e.g:

describe('<Page>', () => {
  it('shold be render page title correctly', async () => {
    await page.goto(url)
    const title = await page.title()
    expect(title).toBe('Sara')
  })
})
  • Run npm test in your terminal and see all the tests pass! (hopefully)