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

@naiveroboticist/legacy-auth-web

v1.1.4

Published

React web tools for authentication

Readme

legacy-auth-web

This package provides a set of react-bootstrap tools to allow authentication using the legacy-auth API.

How To Test Your Package Locally

Before publishing, test your package locally using tools like npm link to ensure everything works as expected.

However, using npm link has its flaws. If your components use any hooks like useState, then things are going to fail. This is because the way modules are resolved using that tool, the hooks will be unresolved and you are really going to be frustrated.

What I finally had to do was to hard-link the code into the directory of the target project. A bit of a PITA, but you'll be able to test without problems. And, if you make changes to the hard-linked files, they will be changed in this project as well.

6.1. Using Npm link

npm link is a powerful tool that allows you to create a symbolic link between your local package and another project. This way, you can test your package in another project without having to publish it to npm.

6.2. Navigate to Your Package’s Directory

Open your terminal and navigate to the root directory of your package:

$ cd path/to/legacy-auth-web

6.3. Create a Global Link

Run the following command to create a global link for your package:

$ npm link

6.4. Navigate to Your Test Project where you want to import

Move to the directory of the project where you want to test your stuff. This could be a separate project or a test environment:

$ cd path/to/your/test/project

6.5. Link Your Package

Link your local package to the test project:

$ npm link icons

6.6. Example Usage in Your Test Project

Now that you’ve linked your local icon package to your test project, you can import and use the icons just as you would with any other npm package.

Here’s an example of how you might use your icons in a React component:

// In your React component file
import React from 'react';
import { Icon1, Icon2 } from 'icons';

const MyComponent = () => {
    return (
        <div>
        <Icon1 width={24} height={24} />
        <Icon2 width={24} height={24} />
        </div>
    );
};

export default MyComponent;

Ensure that the icons are rendering correctly in your test project. If you encounter any issues, you can make adjustments to your code in the src directory and re-run the tests.

6.7. Unlinking Your Package

After testing, if you want to unlink your local package, run the following commands:

# In the project where you linked the package
$ npm unlink my-icons-package

# In the directory of your icon package
$ npm -g unlink

Step 7: Login to npm

If you haven’t logged in, use:

$ npm login

Enter your npm username, password, and email.

Step 8: Publish Your Package

Finally, publish your package to npm:

$ npm publish

Congratulations! Your package is now live on the npm registry.

Step 9: Updating Your Package

If you make changes to your code and want to publish an updated version, follow these steps:

  1. Update the version in your package.json file.
  2. Run npm publish again.