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

viacheck-logs-app

v0.0.2

Published

A React component that sums two number.

Downloads

3

Readme

Demo Template

TODO: Short component description.

Demo Template Image

Installation

npm i -S -E @viamericas/demo-react-to-npm-package

Please review webpack.config.js on externals property to check what packages need to install separately because they are not included in the package.

Usage

Import package

import Demo from '@viamericas/demo-react-to-npm-package';

TODO: Describe all special configurations, functions, states and/or property usages.

Create a function to show changes

const onHandleChange = value => {
  console.log(value);
};

Component implementation

<Demo
  inputA="{1}"
  inputB="{20}"
  onHandleChange="{onHandleChange}"
  className={className} {/* css wrapper */}
  t={t || loadTranslation()} {/* i18n */}
/>

inputA, inputB and onHandleChange are required.
t (i18 translation) and className are optional.

example

<Demo inputA="{1}" inputB="{20}" onHandleChange="{onHandleChange}" />

Language

const { t } = useTranslation('translation');

Check dev-test/locales folder for an example.

Styles

This component does not have custom styles.

Check src/styles folder for component styles.


Developer

Hi! It's a guide where you going to can know how packaging project React, build and publish in a repository npm.

Structure directory

| Path | Description | | ---------------- | ------------------------------------------------------------------------------------ | | __test__ | Contain the logic of the files of testings | | build | This folder contains the transpiled code. It is auto-generated by the build command. | | coverage | This folder contains the code coverage. It is auto-generated by the command. | | dev-test | This folder contains the development environment. | | doc | Contains the project's documentation like user story, user case and diagrames. | | node_modules | These directory is generated automatic by use 'npm install'. | | src | Contain your logic of application/component. | | src/assets | Contain your resources like images, fonts... | | src/core/* | Contain your all rules business. | | src/core/hooks | Contain your custom hooks. | | src/index.js | It's application's start |

How to publish the project

Follow the steps below:

  • npm login
  • npm build
  • npm publish or npm publish --scope=<organization_name>
  • npm unpublish --scope=<organization_name> --force

--scope is only necessary if the package name in the package.json file does not have the company name as a prefix. Always the company name must be with the "@-2 at the beginning and a separator "/" at the end.

{
  "name": "@viamericas/demo-react-to-npm-package"
}

Validate weight of package

You can run the next commands to see the result of the bundle :

  • npm run build:debug
  • npm run analizedependences

Need to have installed source-map-explorer globally.

npm install -g source-map-explorer