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

ref-boilerplate-infrastructure

v1.0.1-dev.12

Published

Infrastructure boilerplate template

Downloads

2

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

minfos.adminminfos.admin

Keywords

Readme

Infrastructure boilerplate template

{Explain the package, its purpose etc}

This repository is the base reference template for a standard package

Folders

  • /.vscode/ - Configuration for Visual Studio Code

  • /build/ - Build scripts and other assets needed for building.

  • /dist/ - Distributable files - static and generated by the build process.

  • /doc/ - Documentation; technical details and the output of any generated documentation

  • /samples/ - Samples that demonstrate the use of the package

  • /spec/ - Specifications; feature files, specialised specs such as load testing. Also any scripts needed for executing the specs.

  • /src/ - The source code, including unit tests

  • /temp/ - Temporary files that are discardable. (Not checked in to source control)

  • /tools/ - Executable binaries and other scripts

  • /vendor/ - Third-party executable binaries and other scripts

Files

  • /.editorconfig - Standardised IDE configuration using EditorConfig

  • /.gitignore - Filename patterns for Git to ignore

  • /bitbucket-pipelines.yml - Configuration for BitBucket pipelines CI

  • /CHANGELOG.md - Log of significant changes per release

  • /mocha.opts - Configuration for the Mocha test runner

  • /package.json - NPM package configuration

  • /README.md - Entry point to the repository’s documentation (this file)

  • /tslint.json - Typescript Lint configuration

Getting set up

{Include here, any extra dependencies and external set-up steps that are required.}

The standard process is to install any required package dependencies by running the command:

npm install

Configuration

The primary mechanism for runtime configuration is to use predetermined environment variables. These can be set in operating system prior to execution, or injected at runtime using the commands cross-env and/or env-cmd.

Configurable variables

| Name | Default | Description | |------------|-------------|---------------------------| | SAMPLE_VAR | sample | This is a sample variable |

Further documentation