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

sandeepulusanisirva-feature-a

v1.0.7

Published

Feature A React Native component

Readme

Feature A

Install the package in a React or React Native project:

npm install sandeepulusanisirva-feature-a

Use the component and pass a title:

import FeatureA from "sandeepulusanisirva-feature-a";

export default function App() {
  return <FeatureA title="Welcome to Feature A" />;
}

The package uses a react-native-web export for React browser apps and a React Native export for native apps.

Plain MVC Usage

Plain MVC apps cannot import npm packages directly from a Razor or HTML view. The browser does not know how to resolve package names like sandeepulusanisirva-feature-a from node_modules.

This will not work directly in a Razor or HTML view:

<script>
  import FeatureA from "sandeepulusanisirva-feature-a";
</script>

Instead, add a small frontend build step that bundles the React component into a browser-ready JavaScript file.

Install the frontend dependencies in the MVC project:

npm install react react-dom sandeepulusanisirva-feature-a
npm install -D vite typescript @vitejs/plugin-react

Create a React entry file:

// src/feature-a-entry.tsx
import React from "react";
import { createRoot } from "react-dom/client";
import FeatureA from "sandeepulusanisirva-feature-a";

const root = document.getElementById("feature-a-root");

if (root) {
  createRoot(root).render(<FeatureA title="Hello from MVC" />);
}

Build the frontend bundle:

npx vite build

Mount the bundled React component from the MVC view:

<div id="feature-a-root"></div>
<script type="module" src="/dist/assets/feature-a-entry.js"></script>

The MVC app does not need to become a full React single-page app. It only needs a small frontend bundle mounted into the view where the component should appear.

Publishing

Before publishing a new version, update the version in package.json, then run:

npm run build
npm pack --dry-run
npm publish --access public