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

@matech-studios/fe-react-lib

v1.7.3

Published

Matech's common functionalities for FE TypeScript projects

Downloads

119

Readme

fe-react-lib

npm version npm downloads

Matech's common functionalities for FE TypeScript projects

  • Direct npm link: https://www.npmjs.com/package/@matech-studios/fe-react-lib

Installation

  • npm: npm install @matech-studios/fe-react-lib
  • yarn: yarn add @matech-studios/fe-react-lib

Package Availability

  • npmjs (default): Published publicly to npm. The commands above work without extra configuration. Direct: https://www.npmjs.com/package/@matech-studios/fe-react-lib
  • GitHub Packages (mirror): Also published to GitHub Packages. Requires auth if your .npmrc routes the @matech-studios scope to GitHub (see below). Direct: https://github.com/orgs/Matech-Studios/packages?repo_name=fe-react-lib

Install from GitHub Packages (optional)

GitHub Packages requires authentication even for public packages. Configure your project-level .npmrc (recommended). Do not commit a real token:

@matech-studios:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${GITHUB_PACKAGES_TOKEN}  # provided via CI/your shell
  • Create a GitHub Personal Access Token with read:packages (classic) and set it as GITHUB_PACKAGES_TOKEN in your environment or CI.
  • Then install as usual:
npm install @matech-studios/fe-react-lib
# or
yarn add @matech-studios/fe-react-lib

Quick Start

  1. Provide Firebase runtime config as early as possible (e.g., in index.html or a bootstrap script):
<script>
  window.__RUNTIME_CONFIG__ = {
    FIREBASE_API_KEY: '...your api key...',
    FIREBASE_AUTH_DOMAIN: '...your auth domain...',
    FIREBASE_PROJECT_ID: '...your project id...',
    FIREBASE_STORAGE_BUCKET: '...your storage bucket...',
    FIREBASE_MESSAGING_SENDER_ID: '...your sender id...',
    FIREBASE_APP_ID: '...your app id...',
    FIREBASE_MEASUREMENT_ID: '...your measurement id...'
  };
  // Ensure this runs before your React app mounts
  // Note: Firebase API keys are not secrets. Restrict usage in GCP (HTTP referrers, package names, etc.).

</script>
  1. Wrap your app with providers:
import React from 'react';
import ReactDOM from 'react-dom/client';
import { LoadingProvider, UserProvider } from '@matech-studios/fe-react-lib';
import App from './App';

ReactDOM.createRoot(document.getElementById('root')!).render(
  <LoadingProvider>
    <UserProvider>
      <App />
    </UserProvider>
  </LoadingProvider>
);
  1. Use hooks and services:
import { useAuth, useUser } from '@matech-studios/fe-react-lib';

export function LoginForm() {
  const { firebaseLogIn } = useAuth();
  const { user, logOut } = useUser();

  const onLogin = async () => {
    await firebaseLogIn('[email protected]', 'password123');
  };

  if (user) return <button onClick={logOut}>Log out</button>;
  return <button onClick={onLogin}>Log in</button>;
}
  1. Social login example (popup):
import { auth, signInWithPopup, googleLoginProvider } from '@matech-studios/fe-react-lib';

await signInWithPopup(auth, googleLoginProvider);

Security

Required envs in the destination project:

window.__RUNTIME_CONFIG__.FIREBASE_API_KEY
window.__RUNTIME_CONFIG__.FIREBASE_AUTH_DOMAIN
window.__RUNTIME_CONFIG__.FIREBASE_PROJECT_ID
window.__RUNTIME_CONFIG__.FIREBASE_STORAGE_BUCKET
window.__RUNTIME_CONFIG__.FIREBASE_MESSAGING_SENDER_ID
window.__RUNTIME_CONFIG__.FIREBASE_APP_ID
window.__RUNTIME_CONFIG__.FIREBASE_MEASUREMENT_ID

Testing locally

  • cd to the project where you want to use the lib.
  • Either use relative or absolute paths:
    • Relative: yarn add file:'..\..\@matech\fe-react-lib\'
    • Run yarn add file:'D:\src\Matech\@matech\fe-react-lib\'

Important notes

  • Do not use path-mapping, this gives errors when testing locally with yarn add file:'some project path'