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

@dlw-digitalworkplace/node-sppkg-deploy

v1.2.0

Published

This gulp plugin allows you to deploy SharePoint packages in the AppCatalog.

Downloads

32

Readme

SharePoint APP Package Deployment

NPM

This is a project created for automating the deployment process of SharePoint application packages in the App Catalog site.

Installation

Run the following command to install the node-sppkg-deploy:

$ npm install node-sppkg-deploy --save-exact

Usage

Once you installed this dependency, you can make use of it with the following provided sample code:

const sppkgDeploy = require('node-sppkg-deploy');

sppkgDeploy.deploy({
    username: "username", // The user that will deploy the file
    password: "password", // The password of the user
    tenant: "tenant", // The tenant name. Example: contoso
    site: "sites/catalog", // Path to your app catalog site
    filename: "app.sppkg", // Filename of the package
    skipFeatureDeployment: true, // Do you want to skip the feature deployment (SharePoint Framework)
    verbose: true // Do you want to show logging during the deployment
});

// OR

sppkgDeploy.deploy({
    username: "username", // The user that will deploy the file
    password: "password", // The password of the user
    tenant: "tenant", // The tenant name. Example: contoso
    absoluteUrl: "https://tenant.sharepoint.com/sites/catalog", // Absolute path to the app catalog site
    skipFeatureDeployment: true, // Do you want to skip the feature deployment (SharePoint Framework)
    verbose: true // Do you want to show logging during the deployment
});

// OR

sppkgDeploy.deploy({
    username: "username", // The user that will deploy the file
    password: "password", // The password of the user
    absoluteUrl: "https://sharepoint.contoso.com/sites/catalog", // Absolute path to the app catalog site
    sp2016: true // SharePoint 2016 On-Prem
    verbose: true // Do you want to show logging during the deployment
});

Arguments / options

The following arguments / options can be passed for deploying the package.

username (required)

Type: String Default: ""

Sets the username to be used for the deployment.

password (required)

Type: String Default: ""

Sets the password to be used for the deployment.

tenant (optional)

Type: String Default: ""

Sets the tenant name to be used for the deployment. Example: https://<tenant>.sharepoint.com

Important: You have to specify this property or the absoluteUrl property

site (optional)

Type: String Default: ""

Specify the relative path to the app catalog site. Example: "sites/catalog"

Important: You have to specify this property or the absoluteUrl property

absoluteUrl (optional)

Type: String Default: ""

Sets the absoluteUrl to the app catalog site that needs to be used for the deployment. Example: https://tenant.sharepoint.com/sites/catalog.

Important: You have to specify this property or the combination tenant and site property.

filename (required)

Type: String Default: ""

The name of the package that needs to be deployed.

skipFeatureDeployment (optional)

Type: Boolean Default: true

Specify if you want to skip feature deployment. When set to true, your customizations will be tenant-scoped.

More information about the skipFeatureDeployment option can be found here: Tenant-Scoped solution deployment for SharePoint Framework solutions.

sp2016 (optional)

Type: Boolean Default: false

Specify if this is SP2016 on-prem.

filename (optional)

Type: Boolean Default: false

Specify if you want to show the console logs.

Where can this be used?

This dependency can for example be used in your SharePoint Framework release process. Here is a sample gulp task that you can add to your SPFx project:

const sppkgDeploy = require('node-sppkg-deploy');

const environmentInfo = {
  "username": "",
  "password": "",
  "tenant": "",
  "catalogSite": ""
}

build.task('sppkg-deploy', {
  execute: (config) => {
    environmentInfo.username = config.args['username'] || environmentInfo.username;
    environmentInfo.password = config.args['password'] || environmentInfo.password;
    environmentInfo.tenant = config.args['tenant'] || environmentInfo.tenant;
    environmentInfo.catalogSite = config.args['catalogsite'] || environmentInfo.catalogSite;

    const pkgFile = require('./config/package-solution.json');
    if (pkgFile) {
      // Retrieve the filename from the package solution config file
      let filename = pkgFile.paths.zippedPackage;
      // Remove the solution path from the filename
      filename = filename.split('/').pop();
      // Retrieve the skip feature deployment setting from the package solution config file
      const skipFeatureDeployment = pkgFile.solution.skipFeatureDeployment ? pkgFile.solution.skipFeatureDeployment : false;
      // Deploy the SharePoint package
      return sppkgDeploy.deploy({
        username: environmentInfo.username,
        password: environmentInfo.password,
        tenant: environmentInfo.tenant,
        site: environmentInfo.catalogSite,
        filename: filename,
        skipFeatureDeployment: skipFeatureDeployment,
        verbose: true
      });
    }
  }
});

Once this task is in place, you can run it with: gulp sppkg-deploy or gulp sppkg-deploy --username "" --password "" --tenant "" --catalogsite "".

More information about using arguments in SPFx gulp tasks can be found here: Passing arguments with custom Gulp tasks for SharePoint Framework projects.

Output of the task:

Gulp task output