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

@diyawanna/my-first-package

v1.0.1

Published

My first npm test package

Readme

📦 @diyawanna/my-first-package

My first NPM test package — a simple utility that says hello 👋
Published by @diyawanna


✨ Features

  • 🔹 Lightweight and easy to use
  • 🔹 Returns a custom greeting
  • 🔹 Useful as a base template for future NPM packages

🚀 Installation

Install the package via NPM:

npm install @diyawanna/my-first-package

🔧 Usage

In JavaScript (CommonJS)

const { sayHello } = require('@diyawanna/my-first-package');

console.log(sayHello("World"));
// Output: Hello, World! From @diyawanna package.

In TypeScript / ES Modules

import { sayHello } from '@diyawanna/my-first-package';

console.log(sayHello('Diyawanna'));
// Output: Hello, Diyawanna! From @diyawanna package.

🔍 Local Development & Testing

A. Link the Package Locally

In your package directory:

npm link

In your consuming project (e.g., Ionic or Laravel):

npm link @diyawanna/my-first-package

B. Use in Your Project

Example for Ionic Angular:

import { sayHello } from '@diyawanna/my-first-package';

console.log(sayHello('Ionic App'));

Example for Laravel (with a frontend build):

import { sayHello } from '@diyawanna/my-first-package';

console.log(sayHello('Laravel'));

C. TypeScript Support (Optional)

If using TypeScript:

  1. Add a tsconfig.json file.

  2. Compile the source with:

tsc

🛠️ Development Commands

  • 🔧 Build (if using TypeScript): tsc
  • 🔄 Link to another project: npm link @diyawanna/my-first-package
  • Unlink when done: npm unlink @diyawanna/my-first-package

📦 Publishing to NPM

To publish your package publicly (required for scoped packages like @diyawanna/*):

npm publish --access public

ℹ️ Without --access public, scoped packages are private by default.

📁 Repository Structure

my-first-package/
├── index.js            # Entry point
├── package.json        # Package metadata
└── README.md           # This file

🧪 Example Function

index.js

function sayHello(name) {
  return `Hello, ${name}! From @diyawanna package.`;
}

module.exports = { sayHello };

🐛 Issues & Feedback

Have a suggestion, question, or bug report?

👉 Open an issue on GitHub

📄 License

MIT License

🙌 Author

Made with ❤️ by @wsmr
Published under the @diyawanna namespace.

🔗 Useful Links


✅ After Saving It

  1. Place this in your project root as README.md.
  2. Run:
    npm publish --access public