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

sp-engineer

v1.0.8

Published

A command-line tool with version control for SharePoint site columns, content types, lists, views, and more

Downloads

5

Vulnerabilities

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

Links

Git

Maintainers

kyleschaefferkyleschaeffer

Keywords

sharepointversion controlconfiguration

Readme

Engineer

npm GitHub issues GitHub license Twitter

Engineer is a powerful command-line tool to help track and consolidate SharePoint configuration changes in any number of environments. It's like version control for site columns, content types, lists, views, and more.

Explore Engineer Documentation

Engineer is inspired by Laravel migrations, and is made possible by PnP-JS-Core, node-pnp-js, and CSOMNode.

Table of Contents

Getting Started

npm i -g sp-engineer

Once installed, you can type engineer into any console prompt to run Engineer commands. Use engineer -h to see a list of commands.

Start a New Project

engineer init

The init command creates env.js in the current working directory. This file contains important configuration information such as the SharePoint site URL and authentication settings. Any authentication configuration supported by node-sp-auth can be used as the auth settings in your env.js file.

Install Engineer Lists

Once your env.js file is set up, you're ready to install Engineer lists to your target SharePoint environment.

engineer install

Migrations

Engineer uses migrations to track configuration changes made to SharePoint. You can use migrations to create a queue of tasks that are executed in order on any number of target environments. Think of migrations like source control for your configuration operations.

New Migration

engineer make my-first-migration

The make command creates a file called migrations/YYYYMMDDHHMMSS-my-first-migration.js (YYYYMMDDHHMMSS is replaced by the current UTC timestamp). Feel free to open this file to see what's inside. By default, new migrations are configured to create a new list called My List when migrated.

Migrate

engineer migrate

The migrate command activates pending migrations. A new list called My List will be created on the target SharePoint site when this migration is activated.

Roll Back

engineer rollback

The rollback command retracts active migrations. Once rolled back, My List is deleted from the target SharePoint site.

Multiple Environments

You can create copies of env.js, allowing you to store authentication and configuration for multiple SharePoint environments. Use Engineer's --config option to switch environments when running any command.

engineer -c env/dev.js migrate
engineer -c env/prod.js migrate

Documentation

Find details on every Engineer command and migration API method in the official documentation, available at http://sp-engineer.org.

Authors

Engineer was created by @kyleschaeffer and Spiritous.

Copyright and License

Code and documentation copyright 2017, Engineer contributors and Spiritous, LLC. Code released under the MIT License. Documentation released under Creative Commons.