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

@nauto/web-apps-archetype

v2.1.1

Published

Builder archetype for Nauto's frontend applications

Downloads

7

Readme

Web Apps Archetype

This package contains the builder archetype for Nauto's web applications.

Scripts

The following scripts are provided by the archetype and are meant to provide sensible defaults for development workflows on our web applications. They leverage a project's local tsconfig.json and tslint.json to determine which files are relevant for a particular script.

ENV variables

We're using webpack to inject some global variables to be used by both your application and by your build tooling:

  • process.env.NODE_ENV
    • Is set to 'development' if unspecified or using NODE_ENV=development, and to 'production' otherwise.
  • process.env.APP_ENV
    • Is set to the value of NODE_ENV
    • e.g. in NODE_ENV=staging ne builder build, process.env.APP_ENV will be 'staging', and process.env.NODE_ENV will be 'production'

start

Runs a webpack dev server with hot module reloading using the archetypal webpack configuration.

build

Runs webpack with the archetypal webpack configuration. Outputs to the dist/ folder. Minimizes, splits code, and generates source maps. In order to build for a particular environment, you'll need to set NODE_ENV appropriately:

NODE_ENV=production ne builder run build

server

Runs an express server serving static files from dist/; typically used with the build script to serve its output.

lint

Runs tslint against the files specified in your local tsconfig.json

test

Runs jest with the archetypal configuration.

Examples

The following examples can be run from within a project using builder and this archetype:

# list all available scripts
ne builder

# run an archetypal script
# (behavior can be overridden with a local script of the same name)
ne builder run <script-name>

Publishing to NPM

Publishing is done via scripts in the root; see the relevant section of the README.

Technology

  • Node 8
  • Yarn
  • Typescript 2.7
  • Webpack 3
  • React 16
  • React-Router 4
  • Redux
  • Styled-components
  • Jest
  • Cypress