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

ns-plugin-with-hooks

v0.1.0

Published

Used for testing hooks execution.

Readme

ns-plugin-with-hooks

Used for testing hooks execution.

Using with AppBuilder

$ appbuilder create native app1 --template HelloWorld
$ appbuilder plugin add ns-plugin-with-hooks --path app1
$ appbuilder deploy android --path app1

In case hooks are working you'll find several changes in the running application:

  1. Top ActionBar will contain the following information Hooks replaced your ActionBar.
  2. Button content will be Hooks everywhere, tap or not, they'll get you.
  3. When starting the application, in the device logs you'll notice the following message: ViewModel is created by your Hooks. You are out of control now..
  4. When tapping the button you'll see the following line in the device logs: You've tapped on the Hooks Button. Remaining taps: ${some number}.
  5. When all 42 taps are done, on device you'll see: Hoorraaay! You have been caught by NativeScript CLI's hooks!.
  6. Additional hooks.txt file will be created in the built application (.apk, .ipa). The content will be: Hooks created this file for you.. It's location is: <unzipped .apk>/assets/app/hooks.txt for Android builds and <unzipped .ipa>/Payload/NativeScript250/app/hooks.txt for iOS builds.

In case hooks are not working, none of the above will work.