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

diegossj-publish-projects

v0.1.8

Published

runs publish on csproj files via msbuild

Downloads

4

Readme

Pentia.Builder

configuration files

solution-config.json:

Contains all the environment specific settings for the solution

  • AlwaysApplyName: is the name that will be used to identify configuration transform files that will always be run. forexample web.always.config will always be applied if the setting is set to "always"
  • showError: Controls if the msbuild will output errors or not
  • showStandardOutput: Controls if the standard output of the msbuild tasks will be shown in the commandline
  • toolsversion: Determines which version of the msbuild tools are being used
  • verbosity: controls the level of verbosity for the msbuild tasks
  • location: is the path to where the frontend project is placed
  • configs: is a array of the build configurations and their settings
  • name:is the name of the configuration, this should match the name of the build configuration in visual studio
  • websiteRoot: the path to root of the website
  • websiteDataRoot: the path to the root of the data folder for the website

solution-packages.json:

Contains the list of packages nessecary for the solution to run.

All packages needs to be a NuGet Package. The nuget package needs to have two folders inside it, one called data and one called website. The data folder will be copied to the path in the solution-config.json setting called websiteDataRoot The website folder will be copied to the path in the solution-config.json setting called websiteRoot

  • packageName: Name of the nuget package in the feed

  • version: the specific version of the package to be installed

  • location: the location where the file is located, can be a file share, or http feed.

Features

  1. Get Sitecore
  2. Publish site to local webroot
  3. Install Packages from packages.json to local webroot
  4. Do configuration transforms