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

@saithodev/ts-appversion

v2.2.0

Published

Reads the version from your packages.json and saves it in a .ts file you can include into your application.

Downloads

2,196

Readme

TS-AppVersion

Build Status Quality Gate Status npm version npm license Known Vulnerabilities Dependency Status semantic-release Commitizen friendly FOSSA Status

This package extracts version information from your package.json and Git (if configured) and saves it into a TypeScript file. You can then access that TypeScript file from your application and display the version in your app.

The examples below illustrate the usage of this package for the Angular framework. However it should work similarly for any other JavaScript framework that is using TypeScript.

Getting started

The package comes with a script that has to be run before your application is built. You might want to use prestart and prebuild inside your package.json for that:

{
  scripts: [
    "prestart": "ts-appversion",
    "start": "ng serve",
    "prebuild": "ts-appversion",
    "build": "ng build",
  ]
}

With that setup the file is updated when npm start and npm build are run. Note: You won't be able to run ng build anymore as the script will not be executed. Use npm build instead.

Command arguments

| Argument | Meaning | Default | |---|---|---| | --root | root directory where your package.json is located | . | | --file | relative location of the output file (based on the root directory) | ./src/_version.ts | false | | --git | relative location of the folder containing the .git folder (based on the root directory) | . | | --pnpm | PNPM has a different folder structure, resulting in a different root level. Add this if you use PNPM to install your dependencies. If package.json is not found at the expected PNPM path, it will fall back to the default one. This setting is ignored if --root is an absolute path. | false | | --set-version | Set this to override the value of the version string fetched from package.json (set in version property) | |

Receiving the versions

The script generates a TypeScript file at the location ./src/_versions.ts if you haven't provided a different location. You'll be able to import the values just like any other package, if you want use just versions information, like in environment.ts example file:

import versions from '../_versions';

or you can import also TsAppVersion and use directly in your template, like in app.component.ts example file

import { TsAppVersion, versions } from 'src/_versions.ts';

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent { 
  public readonly tsAppVersion: TsAppVersion;
  constructor() {
    this.tsAppVersion = versions;
  }
}

The file will export an object with following variables:

  • version is the version from packages.json (or value of set-version option if set)
  • name is the name from the packages.json (e.g. 'sample-app')
  • description is the description from the packages.json
  • versionDate is the timestamp in ISO format when the compilation/package started.
  • versionLong is the version from the packages.json PLUS the Hash of the current Git-Commit (e.g. v1.0.0-g63962e3) - will only be generated if your repository is a Git Repository
  • gitTag is the latest Git tag
  • gitCommitHash is the short hash of the last commit
  • gitCommitDate is the timestamp in ISO format of the last commit

Note: The variables starting with "git" and the variable "versionLong" will only be available for Git repositories.

Environment-related versions

In some cases it might be better to not display the version number or only the short notation. You can use the environments to display different version informations.

In the following example:

  • the dev environment will display the version timestamp
  • the staging environemnt will diplay the long version (with the Commit hash)
  • the production environment will display the simple notation

environments/environment.ts

import versions from '../_versions';
export const environment = {
  production: false,
  version: versions.versionDate,
};

environments/environment.staging.ts

import versions from '../_versions';
export const environment = {
  production: false,
  version: versions.versionLong,
};

environments/environment.prod.ts

import versions from '../_versions';
export const environment = {
  production: true,
  version: versions.version,
};

From there you can access the version inside the Component which should display the version, e.g.:

import { Component } from '@angular/core';
import { environment } from '../environments/environment';
@Component({
  selector: 'app-root',
  template: '{{title}} {{version}}'
})
export class AppComponent {
  title = 'app';
  version = environment.version ? 'v' + environment.version : '';
}

Check out the example/ directory for a working example Angular application.

License

FOSSA Status