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

nativescript-dev-multiple-env

v2.0.0-beta5

Published

A Hook For Nativescript to allow multiple Environments

Downloads

7

Readme

nativescript-dev-multiple-environments

This Hook is made for using multiple environments within a nativescript application.

What it does

First it changes your packageId to whatever you have stated in your environment-rules.json

it also copies any files you have suffixed with the name of the environemnt for example : App_Resources/Android/google-services.staging.json will get copied to App_Resources/Android/google-services.json before building.

Selecting Environment

Once you have a initial environment-rules.json file you can change between the environments using --env.use.ENV_NAME

for example for ios: tns run ios --env.use.staging

this can also be used with other --env args like:

tns run ios --bundle --env.aot --env.uglify --env.use.release

Environments

a basic environment-rules.json file is generated for you it looks like this:


{
    "version": "1.0.0",
    "default": "staging",
    "extraPaths": [
        'app/environments'
    ],
    "environments": [
        {
            name: "staging",
            packageId: "org.nativescript.appName.staging",
            copyRule: "(.*\\.staging\\..*)"
        },
        {
            name: "release",
            packageId: "org.nativescript.appName.release",
            copyRule: "(.*\\.release\\..*)"
        }
    ]
}

You can tweak this however you want, and add as many environments as you like.

ExtraPaths is Optional, but can add multiple paths within the app. these will follow the same rules for the rules.