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 🙏

© 2025 – Pkg Stats / Ryan Hefner

natively

v2.22.0

Published

Natively SDK for building native-like web applications

Readme

Plain HTML Header Injection

Installation

Put the following code in your website header (between <head></head> tags):

<head>
<script async onload="nativelyOnLoad()" src="https://cdn.jsdelivr.net/npm/[email protected]/natively-frontend.min.js"></script>
<script>
function nativelyOnLoad() {
    window.natively.setDebug(true); // To see errors
}
</script>
</head>

You can specify an SDK version by replacing version number 2.14.0. The latest version number can be found in this repo. Debug mode which enables native alerts with errors. It's can be very useful while you developing a website.

Usage

// Elements (with callback from the App)
const notifications = new NativelyNotifications();
const playerId_callback = function(resp) {
    console.log(resp);
    console.log(resp.playerId);
};
notifications.getOneSignalId(playerId_callback);

// Actions (without callback from the App)
window.natively.shareText("Hello world!");

🛠 React/NextJS (min version 2.15.0)

Installation:

npm i natively@">=2.15.0"

Usage:

'use client'; // <--- THIS IS IMPORTANT, Natively can't be used on server side
import { NativelyInfo, useNatively } from 'natively';

export default function Home() {
    const natively = useNatively(); // <--- useNatively is just a wrapper on window.natively
    const info = new NativelyInfo();
    const browserInfo = info.browserInfo();
    const openConsole = () => {
        natively.openConsole();
    };
    console.log(browserInfo);
    return (
        <div>
            Check the console for browser info. isNativeApp: {browserInfo.isNativeApp ? "true" : "false"}
            <button onClick={openConsole}>Open Console</button>
        </div>
    );
};

Important for NextJS users make sure to add 'use client' to the component where you're using Natively SDK. "useNatively" is referring to "window.natively" everywhere in this documentation.

Example project: https://github.com/romanfurman6/nextjs-boilerplate

Debugging (Inspect console inside of mobile app)

// Make sure you have JS SDK >=v2.7.2
window.natively.openConsole();  

// NextJS/React
import { useNatively } from 'natively';
const natively = useNatively();
natively.openConsole();

Release new version (for developers)

  1. login to npm registry
  2. npm run build
  3. git commit...
  4. npm version patch/minor/major
  5. git push...
  6. npm publish
  7. Create a new release in GitHub

More in documentation