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

@draftbit/core

v49.4.10

Published

Core (non-native) Components

Downloads

22,401

Readme

@draftbit/core

This module contains web-compatible components used by @draftbit/ui.

You should look @ @draftbit/ui if you are just looking to use these components in your own projects.

This module is consumed by the ui module, which injects native dependencies and re-export the components with those dependencies included for react-native projects.

It is possible, but not advised, to directly consume components from this module in your own web projects. You will have to inject your own compatible dependencies. This is how this project is consumed internally by Draftbit to power our builder experience. See the interfaces folder to see what you'll need to implement yourself.

Contributing

If you're looking to contribute to components in @draftbit/ui this is usually the module you're looking for. Checkout @draftbit/native if you need to add a module with a native dependency. But please open a PR to discuss first. It's possible! There's just some gotcha's we should talk through before you start.

Note on Dependencies

@draftbit/native can (and should) depend on this module when composing components to create higher-order functionality, and to share interfaces. This module should never depend on @draftbit/native, directly or otherwise, as that will break non-Expo toolchains that expect to be able use @draftbit/core directly.