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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@morrigu/core

v1.0.4

Published

This guide provides an overview of how to configure the `@morrigu/core` package for use in your React applications. `@morrigu/core` offers a suite of React hooks for interacting with the Morrigu SaaS product, including feature flagging and prompt manageme

Downloads

9

Readme

Configuration Guide

This guide provides an overview of how to configure the @morrigu/core package for use in your React applications. @morrigu/core offers a suite of React hooks for interacting with the Morrigu SaaS product, including feature flagging and prompt management based on environmental settings.

Getting Started

Before you begin, ensure you have node and npm/yarn installed on your machine. This guide assumes you have basic knowledge of React and environment variable management in a development project.

Installation

To use @morrigu/core in your project, install it via npm or yarn:

npm install @morrigu/core

Or, if you're using Yarn:

yarn add @morrigu/core

Configuration

@morrigu/core requires specific environment variables to be set for authentication and API interaction:

  • MORRIGU_SECRET_KEY: Your Morrigu application's secret key.
  • MORRIGU_CLIENT_ID: The client ID for your Morrigu application.

Setting Environment Variables

Development Environment

For local development, you can set these variables in a .env.local file at the root of your project:

MORRIGU_SECRET_KEY=your_secret_key_here
MORRIGU_CLIENT_ID=your_client_id_here

Make sure to add .env.local to your .gitignore file to prevent secret leakage.

Production Environment

In production, set the environment variables through your hosting provider's dashboard. For example, if you're using Vercel or Netlify, you can add environment variables in the project settings.

Using @morrigu/core

After configuring the environment variables, you can start using @morrigu/core in your React components.

import React from 'react';
import { useFeatureFlag } from '@morrigu/core';
import { usePrompt } from '@morrigu/core';

const MyComponent = () => {
  const [prompt, {completion, reset, stream}] = usePrompt('my-prompt');

  return (

  );
};

export default MyComponent;

License

@morrigu/core is open-source software licensed under the MIT license.


This README provides a basic structure for configuring and getting started with your package. Remember to replace placeholder texts like `your_secret_key_here`, `your_client_id_here`, and repository URLs with actual information relevant to your project.