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

@gtcx/screens-mobile

v0.1.0

Published

GTCX mobile screen library — enterprise screens for React Native

Readme

@gtcx/screens-mobile

Enterprise screen components for GTCX mobile applications. 18 full-page screens covering auth, dashboard, settings, search, document review, notifications, onboarding, and more.

Installation

pnpm add @gtcx/screens-mobile

Peer dependencies:

pnpm add react-native nativewind @gtcx/ui-mobile @gtcx/layouts-mobile

Usage

import { SignInScreen, DashboardScreen, DocumentScreen } from '@gtcx/screens-mobile';

// All screens are zero-business-logic — all state via props
function App() {
  return (
    <SignInScreen
      onSubmit={({ email, password }) => auth.signIn(email, password)}
      loading={auth.loading}
      error={auth.error}
    />
  );
}

Screens

Phase M — Core enterprise (12)

| Screen | Description | Key props | | ----------------------- | ----------------------------------------------- | --------------------------------------------- | | SignInScreen | Email/password sign-in form | onSubmit, loading, error | | SignUpScreen | Registration form | onSubmit, loading, error | | ForgotPasswordScreen | Email reset request | onSubmit, loading, success, error | | OtpVerificationScreen | 6-digit OTP input | onSubmit, onResend, loading, error | | DashboardScreen | KPI stats, activity feed, quick actions | stats, activity, actions, onAction | | AccountScreen | Profile view with avatar and nav sections | user, sections, onItemPress | | DataListScreen | Filterable, sortable, paginated data table | columns, rows, filters, onSort | | DetailScreen | Key-value entity detail with status and actions | title, sections, statusBadge, actions | | ApprovalsScreen | Approval queue with approve/reject per item | items, onApprove, onReject | | MembersScreen | Team member list with roles and invite | members, onMemberPress, onInvite |

Phase O — Enterprise extensions (6)

| Screen | Description | Key props | | --------------------- | ----------------------------------------------- | ----------------------------------------------- | | NotificationsScreen | Grouped notifications, unread badge, dismiss | notifications, onMarkAllRead, onDismiss | | TimelineScreen | Activity/audit history with filter tabs | entries, filters, onFilterChange | | SettingsScreen | iOS-style grouped settings: toggle, nav, action | sections, onItemPress, onToggleChange | | SearchScreen | Full-page search with recents, filters, results | value, onChangeText, recents, results | | DocumentScreen | Document viewer: metadata, attachments, audit | meta, attachments, auditTrail, actions | | OnboardingScreen | Multi-step onboarding with Stepper and Progress | steps, currentStepIndex, onNext, onBack |

Design principles

Zero business logic. Every screen is a pure UI component — all state, data, and callbacks flow in via props. No API calls, no routing, no stores inside screens.

Prop-driven state. Loading skeletons, empty states, error banners, and success messages are all controlled by props (loading, error, success, emptyMessage). The parent owns state; the screen renders it.

Consistent testID convention. Every screen element has a testID. Sub-elements follow ${testID}-subpart (e.g. document-heading, document-status-badge, document-action-approve). This makes integration testing deterministic.

Architecture

TypeScript shim

This package ships types/react-native.d.ts — a lightweight shim enabling typecheck and DTS generation without installing react-native. It is kept in sync with the source of truth at packages/ui-mobile/types/react-native.d.ts.

When to update the shim: If you add a screen that uses a React Native prop not yet declared (e.g. a new TextInput prop), add it to this shim AND to the matching shims in ui-mobile and layouts-mobile.

When to update the mock: If you use a new React Native component export (e.g. Animated, KeyboardAvoidingView), add it to tests/__mocks__/react-native.tsx.

Stories

Storybook stories live alongside each screen in src/<screen>/<screen>.stories.tsx. They are excluded from the package typecheck (stories are Storybook-only artifacts). The Storybook app at apps/storybook-native/ picks them up via glob.

Testing

pnpm --filter @gtcx/screens-mobile test       # 180 tests
pnpm --filter @gtcx/screens-mobile typecheck
pnpm --filter @gtcx/screens-mobile lint
pnpm --filter @gtcx/screens-mobile build

Contributing

  • Follow the zero-business-logic principle — no API calls inside screens
  • Add testIDs to every rendered element following the ${testID}-subpart pattern
  • Write tests in tests/<phase>.test.tsx grouped by screen
  • Update all three type shims when using a new React Native prop