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

@primitives/border

v3.1.0

Published

The `<Border>` primitive is designed to circumvent a couple of issues that could be source of headaches developing on a broad cross-platform system.

Downloads

40

Readme

The <Border> primitive is designed to circumvent a couple of issues that could be source of headaches developing on a broad cross-platform system.

Usage

import React from 'react'
import { Border } from '@primitives/border'
import { Block } from '@primitives/border'
import { Text } from '@primitives/text'

const HelloWorld = () => (
  <Block>
    <Border
      topWidth={2}
      rightWidth={2}
      bottomWidth={2}
      leftWidth={2}
      color={[240, 0, 230, 1]}
    />
    <Text>Hello World!!</Text>
  </Block>
)

Properties

| Property | Type | Description | Required | | ----------------- | -------- | --------------------------------- | -------- | | Color | TColor | * | yes | | topLeftRadius | number | px to top left radius | | | topRightRadius | number | px to top right radius | | | bottomRightRadius | number | px to bottom right radius | | | bottomLeftRadius | number | px to bottom left radius | | | topWidth | number | px top width | | | rightWidth | number | px right width | | | bottomWidth | number | px bottom width | | | leftWidth | number | px left width | | | overflowBottom | number | px offset from bottom container | | | overflowLeft | number | px offset from left container | | | overflowRight | number | px offset from right container | | | overflowTop | number | px offset from top container | |

*TColor: a tuple that will translate to rgba format, comes Colorido

Borders in Native vs Borders in the Web

CSS box-model offers an alternative in the web which approximates the bounding area to the one designers are more used to think. So, for web it‘s now a widespread good practice to work with box-sizing: border-box set at the top of an application global styles.

Though in React Native it‘s a different story. There is no alternative and the box-model is always content-box. In addition, there aren‘t many display types, being flex the norm there.

This is likely to cause slight discrepancies in the layout that are perceivable to every user and could disrupt the experience when setting borders or using any of the popular border hacks (with wrapping elements).