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

@ontrackms/nativescript-dotenv

v1.5.0

Published

Adds common NativeScript configurations to Dotenv

Readme

NativeScript Dotenv Plugin

Static Badge

NPM Test Workflow GitHub License

Adds common NativeScript configurations to Dotenv

Contents

Installation

npm i -D @ontrackms/nativescript-dotenv

Usage

Add these lines to the exported function in webpack.config.js:

const { NativeScriptDotEnvPlugin } = require("@ontrackms/nativescript-dotenv");

module.exports = (env) => {
  webpack.init(env);
  // must be called after webpack.init
  NativeScriptDotEnvPlugin.init(webpack);
  return webpack.resolveConfig();
};

Configuration

All of the following .env variables are optional ⚙️ — set only the ones you need.

| Variable | Controls | | --- | --- | | NATIVESCRIPT_BUNDLE_ID | The app's bundle identifier, written to package.json's name field. | | NATIVESCRIPT_BUNDLE_VERSION | A semver string (e.g. 3.2.1, or 3.2.1+42 for an explicit build number). Written to package.json's version, iOS's CFBundleShortVersionString/CFBundleVersion, and Android's versionName (see Android versionCode below for versionCode). | | NATIVESCRIPT_APPLE_TEAM_ID | The iOS code-signing team, written to DEVELOPMENT_TEAM in build.xcconfig. |

NATIVESCRIPT_BUNDLE_ID=com.corp.app.test
NATIVESCRIPT_BUNDLE_VERSION=3.2.1
NATIVESCRIPT_APPLE_TEAM_ID=ASDFG1234

Android versionCode

Android's versionCode (in App_Resources/Android/src/main/AndroidManifest.xml) is auto-incremented on release builds only — ns build android --release or ns run android --release — which set webpack's env.production flag.

Regular dev builds (ns run android without --release) leave AndroidManifest.xml untouched, so versionCode doesn't creep up on every rebuild.

Verbose logging

By default, the plugin prints the parsed .env values to the console — handy while developing locally.

Since a .env file may hold secrets unrelated to this plugin, that logging is automatically disabled on CI/cloud builds, detected via the CI environment variable set by virtually every provider (GitHub Actions, GitLab CI, Bitrise, App Center, Codemagic, Travis, etc.).

Override this explicitly with the verbose option:

NativeScriptDotEnvPlugin.init(webpack, { verbose: false });