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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sweatco/styled

v0.2.1

Published

Enjoy the beauty of the `styled-components` combined with the efficiency of `StyleSheet`. This project's objective is to leverage the styled-components library's API, shifting work from runtime to compile time.

Readme

@sweatco/styled

Enjoy the beauty of the styled-components combined with the efficiency of StyleSheet. This project's objective is to leverage the styled-components library's API, shifting work from runtime to compile time.

Setup

  1. Add @sweatco/styled/babel-plugin to your Babel configuration.
module.exports = {
    presets: ['module:metro-react-native-babel-preset',
     
    ],
+   plugins: ['@sweatco/styled/babel-plugin'],
 }
  1. Encapsulate the root component with the ThemeProvider wrapper. This will enable theme-based styling throughout your application.

Example

import React from 'react'

import styled from '@sweatco/styled'

const Title = styled.Text<{ color: string }>`
  font-size: 15px;
  text-align: center;
  color: ${({ color }) => color};
`

const Container = styled.View`
  padding: 4px;
  background: wite;
`

const Screen = () => (
    <Container>
      <Title color="black">Hello World, this is my first styled native component!</Title>
    </Container>
  )

Refs

When using the ref prop, it will refer to the component you are styling rather than the styled component.

const RedView = styled.View`
  background: red;
`

const Component = () => {
    const ref = useRef<View>()

    return <RedView ref={ref} />
}

Under the Hood

  1. The first step is to transpile template literals.

The library utilizes (postcss)[https://github.com/postcss/postcss] (css-to-react-native)[https://github.com/styled-components/css-to-react-native#readme] to parse string templates and build style pairs.

Fixed styles

All fixed styles are converted to object properies without any changes

before:

const Component = styled.View`
    background: white;
    height: 1px;
`

after:

const Component = styled.View({
    backgroundColor: 'white',
    height: 1,
})

substitute styles

For styles utilizing the $ command, we employ the substitute helper. This helper checks whether a style is dynamic or fixed. If the style depends on properties, substitute returns a function designed to be called during render time.

before:

const Component = styled.Text`
    color: ${'white'};
    font-family: ${'Roboto'}-${'Bold'};
    height: ${(props) => props.size}px;
`

after:

const Component = styled.View({
    color: styled.substitute((args) => args[0], ['white']),
    fontFamily: styled.substitute(
        (args) => `${args[0]}-${args[1]}`,
        ['Roboto', 'Bold'],
    ),
    height: styled.substitute(
        (args) => args[0],
        [(props) => props.size],
    ),
})

// ->

const Component = styled.View({
    color: 'white',
    fontFamily: 'Roboto-Bold',
    height: (props) => props.size,
})

runtime styles

If styles cannot be parsed during compile time, they are wrapped with the runtime helper.

runtime helper calls css-to-react-native for passed key and value

before:

const Component = styled.Text`
    border: ${'white'};
    transform: ${I18nManager.isRTL ? 'rotate(180deg)' : 'rotate(0deg)'}
`

after:

const Component = styled.View({
    ...styled.runtime(
        'border',
        styled.substitute((args) => args[0], ['white'])
    ),
    ...styled.runtime(
        'transform',
        styled.substitute((args) => args[0], [I18nManager.isRTL ? 'rotate(180deg)' : 'rotate(0deg)'])
    ),
})

// ->

const Component = styled.View({
    borderWidth: 1,
    borderColor: 'white',
    borderStyle: 'solid',
    transform: [{ rotate: '180deg' }],
})

mixins

All injected constructions, such as ${() => {...}}; or ${css``}, are wrapped with the mixin helper.

before:

const shared = css`
    color: white;
    width: ${(props) => props.size}px;
`

const Component = styled.Text`
    ${shared};
    height: 1px;
`

after:

const shared = {
    color: 'white',
    width: styled.substitute((args) => args[0], [(props) => props.size]),
}

const Component = styled.Text({
    ...shared,
    height: 1,
})