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 🙏

© 2025 – Pkg Stats / Ryan Hefner

react-native-web-toolkit

v1.0.6

Published

A CLI toolkit to seamlessly add web support to React Native projects using Webpack

Readme

React Native Web Toolkit

A CLI toolkit to seamlessly add web support to React Native projects using Webpack.

Features

  • Easy setup of React Native Web in existing React Native projects
  • Automated Webpack configuration
  • Support for both development and production builds
  • Single setup option:
    • Webpack configuration for custom control

Prerequisites

  • React Native >= 0.81.0
  • Node.js and npm installed

Installation

npx react-native-web-toolkit

Troubleshooting

Common Issues

Version Mismatch Errors

  • React Version Mismatch
    Error: Invalid hook call
    Solution: Ensure react and react-dom versions match exactly. For example:
    {
      "dependencies": {
        "react": "19.1.1",
        "react-dom": "19.1.1"
      }
    }

Webpack Configuration Issues

  • @react-native/new-app-screens Error

    Error: Unable to resolve module @react-native/new-app-screens

    Solution: Remove @react-native/new-app-screens imports from App.tsx as they're not supported by react-native-web:

    // Remove this line from App.tsx
    - import { ... } from '@react-native/new-app-screens';
  • React Not Found Error

    Error: React must be in scope when using JSX

    or

    Error: React not found

    Solution: Add React import at the top of your App.tsx:

    import React from "react";
  • Loader Not Found Error

    Module parse failed: Unexpected token
    You may need an appropriate loader to handle this file type

    Solution: Add the problematic package to Babel loader include paths in webpack.config.js:

    {
      test: /\.[jt]sx?$/,
      include: [
        path.resolve(appDirectory, 'node_modules/package-name'),
        // ...other includes
      ],
      use: {
        loader: 'babel-loader'
      }
    }

Build Performance Issues

  • If the build is slow, try:
    • Using cache-loader for frequently used modules
    • Enabling Webpack's cache in development mode
    • Adding heavy dependencies to externals if not needed for web

Development Server Issues

  • If hot reload isn't working:
    • Check if WebSocket connection is established
    • Ensure no port conflicts (default: 8080)
    • Clear browser cache and node_modules/.cache

For more specific issues, please check our GitHub Issues page.