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

@phygitallabs/portal-platform

v6.8.1

Published

This package provides a comprehensive platform setup with Firebase integration, authentication, and various UI components.

Readme

Platform Package

This package provides a comprehensive platform setup with Firebase integration, authentication, and various UI components.

Firebase Configuration

New Dynamic Configuration (Recommended)

Instead of hardcoding Firebase config in JSON files, you can now pass the configuration dynamically through the provider:

import { PlatformProvider, FirebaseConfig } from "@phygitallabs/portal-platform";

const firebaseConfig: FirebaseConfig = {
  apiKey: process.env.REACT_APP_FIREBASE_API_KEY!,
  authDomain: process.env.REACT_APP_FIREBASE_AUTH_DOMAIN!,
  projectId: process.env.REACT_APP_FIREBASE_PROJECT_ID!,
  storageBucket: process.env.REACT_APP_FIREBASE_STORAGE_BUCKET!,
  messagingSenderId: process.env.REACT_APP_FIREBASE_MESSAGING_SENDER_ID!,
  appId: process.env.REACT_APP_FIREBASE_APP_ID!,
  measurementId: process.env.REACT_APP_FIREBASE_MEASUREMENT_ID,
};

function App() {
  return (
    <PlatformProvider
      baseURL="https://your-api-url.com"
      firebaseConfig={firebaseConfig}
    >
      {/* Your app content */}
    </PlatformProvider>
  );
}

Using Firebase Services

Use the provided hooks to access Firebase services:

import {
  useFirebaseAuth,
  useFirebaseFirestore,
  useFirebaseStorage,
  useFirebaseAuthActions,
} from "@phygitallabs/portal-platform";

function MyComponent() {
  const auth = useFirebaseAuth();
  const firestore = useFirebaseFirestore();
  const storage = useFirebaseStorage();
  const { signInWithEmail, signInWithGoogle } = useFirebaseAuthActions();

  const handleLogin = async () => {
    try {
      await signInWithEmail("[email protected]", "password");
    } catch (error) {
      console.error("Login failed:", error);
    }
  };

  return <button onClick={handleLogin}>Login</button>;
}

Migration from Static Config

If you're migrating from the old static configuration (firebase_config.json):

  1. Remove the firebase_config.json file
  2. Update your PlatformProvider to accept firebaseConfig prop
  3. Pass your Firebase configuration through environment variables or other secure methods
  4. Update any direct Firebase imports to use the new hooks

Legacy Support

The package still provides backward compatibility for existing static Firebase imports, but they will show deprecation warnings and require the FirebaseProvider context.

Environment Variables

Set up your environment variables:

REACT_APP_FIREBASE_API_KEY=your-api-key
REACT_APP_FIREBASE_AUTH_DOMAIN=your-project.firebaseapp.com
REACT_APP_FIREBASE_PROJECT_ID=your-project-id
REACT_APP_FIREBASE_STORAGE_BUCKET=your-project.appspot.com
REACT_APP_FIREBASE_MESSAGING_SENDER_ID=123456789
REACT_APP_FIREBASE_APP_ID=1:123456789:web:abcdef
REACT_APP_FIREBASE_MEASUREMENT_ID=G-ABCDEF123