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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@vivintsolar-oss/native-vs-app-link

v1.0.2

Published

Deep linking methods for React Native.

Downloads

2

Readme

@vivintsolar-oss/native-vs-app-link

yarn add @vivintsolar-oss/native-vs-app-link
// or
// npm install @vivintsolar-oss/native-vs-app-link

VSAppLink

A handy little method that will default to the app store if an app that you want to deep link into is not installed on the device.

Demo

openOnDevice

import VSAppLink from '@vivintsolar-oss/native-vs-app-link';

const config = {
  appName: 'Vivint Solar',
  appStoreId: 'id1289441541',
  playStoreId: 'com.vivintsolar.hea',
  appStoreLocale: 'us',
};

VSAppLink.openOnDevice('vslr://+', config)

This is the method you'll want to use most of the time since it will attempt to open up the app on the device and if it doesn't succeed then it will try either openInStore or openInBrowser. You can specify it to use openInBrowser by passing it a downloadLink in the config object.

openInStore

import VSAppLink from '@vivintsolar-oss/native-vs-app-link';

const config = {
  appStoreId: 'id1289441541',
  playStoreId: 'com.vivintsolar.hea',
};

VSAppLink.openInStore(config)

openInBrowser

import VSAppLink from '@vivintsolar-oss/native-vs-app-link';

const config = {
  downloadLink: 'https://www.vivintsolar.com',
};

VSAppLink.openInBrowser(config)

Props

| Name | Default | Type | Description | |:----- |:------ |:---- |:----------- | | url | | string | The schema link to the native app you want to deep link into | | appName | | string | Used as the value used in a thrown error | | appStoreId | | string | ID from the Apple App Store | | playStoreId | | string | ID from the Google Play Store | | appStoreLocale | us | string | Used to specify if the app is only available in the App Store outside of the us. |

Store ID's

appStoreId can be found in the developer console of itunes but the most common way to find it is via the app store itself via the url. For example for this app, https://itunes.apple.com/us/app/vivint-solar/id1289441541?mt=8 the appStoreId would be id1289441541

playStoreId can be found in a similar manner, so for https://play.google.com/store/apps/details?id=com.vivintsolar.hea the playStoreId would be com.vivintsolar.hea