@draftbit/native
Advanced tools
Draftbit components with native dependencies that are incompatable with non-expo
build systems, such as expo-av or @expo/vector-icons.
These components are imported / injected inside the @draftbit/ui library so
that incompatable expo dependencies do not exist in @draftbit/core.
Add new components with such dependecies here.
See IconButton.tsx in core for an
example of a 'hybrid' component API that allows a native component to be
injected for ui and a web-compatible version be injected for web.
FAQs
Draftbit UI Components that Depend on Native Components
We found that @draftbit/native demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
