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

@charlietango/nuget

v7.0.0

Published

Package and publish a NuGet package to a custom feed.

Downloads

337

Readme

NuGet task

Package and publish a NuGet package to a custom feed. This is built for our specific needs on our own internal projects.

Requirements

  • Node 8.x+
  • Mono - For Mac/Linux

Usage

Add the dependency

yarn add @charlietango/nuget --dev

Build your static project into a build directory dist/static, and package it with the Node API:

const nuget = require('@charlietango/nuget');

nuget({
  files: 'dist',
  output: 'output',
});

or calling the bin

$ ct-nuget dist -o output

The NuGet will be packaged and pushed to the feed.

Structure

To avoid polluting the .NET projects, all the files in the NuGet package should be contained in a directory. By default we are using the static directory inside dist dist. Once the NuGet package is installed, a shell script will copy all the files into the project

Config

| Name | Type | Default | Description | | ------------- | ------- | ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | name | string | name from package.json | | | packageId | string | dk.charlietango.{upperFirst(camelCase(name))} | Valid packageId | | version | string | version from package.json | Valid semver version string | | files | glob | dist in project root | The directories and files to add. | | rootDir | string | dist | The root directory. This will be removed from all the paths. | | globOptions | Object | {ignore: ['**/index.html']} | | | author | string | 'Charlie Tango' | | | iconUrl | string | https://ct-assets.netlify.com/React_logo-64.png | | | description | string | description from package.json | | | apiKey | string | process.env.NUGET_API_KEY | | | nugetFeed | string | process.env.NUGET_FEED | | output | string | | Copy the .nupkg file to this directory | | cache | string | node_modules/.cache/nuget | Temp directory to use when building | | legacyInstall | boolean | false | Don't add the powershell tools to copy files into the project after install, and instead use the special "content" directory | | quiet | boolean | false |