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

az-upload

v1.3.4

Published

A tool for quickly packaging and uploading your code to the server

Downloads

30

Readme

az-upload

A tool for quickly packaging and uploading your code to the server

Installation

npm install az-upload --save -dev

or

yarn add az-upload --dev

Usage

Create file "upload.config.js/upload.config.json/.uploadrc" in the project root directory.

Add scripts like this:

// 'env' will be 'production'
"upload": "az-upload"

or

// 'env' will be 'stage'
"upload:stage": "az-upload stage"

configuration

"upload.config.js" example:

module.exports = {
  uploadDir: 'build',
  packingCMD: (env) => {
    if (env === 'production') return 'npm run build'
    return `npm run build:${env}`
  },
  confirm: ['production'],
  environment: {
    production: {
      ip: '',
      port: '',
      username: '',
      password: '',
      path: '',
      rmPath: '',
    },
    stage: {
      ip: '',
      port: '',
      username: '',
      password: '',
      path: '',
      rmPath: '',
    },
  },
}

uploadDir

String

Not required. Default: 'dist'

The files you want to upload. Generally, it is the directory of the packaged code.

packingCMD

Function/Object/String

Not required

The script use to packaging your code. 'env' is from your script.

Example:

module.exports = {
  // Function, default
  packingCMD: (env) => {
    if (env === 'production') return 'npm run build'
    return `npm run build:${env}`
  },
  // Object
  packingCMD: {
    production: 'npm run build',
    stage: 'npm run build:stage',
  },
  // String
  packingCMD: 'npm run build',
}

confirm

Boolean/Array/Function

Not required

Does command execution require confirmation? 'env' is from your script.

Example:

module.exports = {
  // Array, default
  confirm: ['production'],
  // Boolean
  confirm: true,
  // Function
  confirm: (env) => {
    if (env === 'production') return true
    return false
  },
}

environment

Object

Required

'environment[env]' will be used for connecting the server. 'env' is from your script.

ip: ip of server

port: port of server

username: username of server

password: password of server

path: the path to upload your code

rmPath: the path cleaned before uploading