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

@codearts/plugin-packager

v0.0.28

Published

A packager tool for huawei-codearts's plugin.

Downloads

9

Readme

@codearts/plugin-packager

A packager tool for Huawei CodeArts IDE's plugin.

Usage

install codearts plugin-packager

npm install @codearts/plugin-packager --save-dev

run plugin-packager

npx cap

or you can add "pack": "cap package -p" in scripts, then run pack script

npm run pack

Help

  1. cap -h show help of tool.
  2. cap package pack in default mode (development mode), in this mode, all files are packed.
  3. cap package -p pack in production mode, all unnecessary files are excluded.
  4. cap package -i <files>, input which file you want to include, or use batch matching with quotation marks.
  5. cap package -e <files>, input which file you want to exclude, or use batch matching with quotation marks.
  6. You can also create a 'pack-config.json' file in workspace, directly to set files you want to include or exclude like: { "exclude": [], "include": [] }. (See Batch matching rule)
  7. cap package -s, skip npm install before packing.
  8. cap publish, pack in production mode and publish to Marketplace.
  9. cap publish -t 1, Set the release type. "0" indicates the grayscale release, "1" indicates the official release, and the default is grayscale release.

Batch matching rule

  • *.js only match js files in current dir.
  • **/*.js match all js files.
  • path/*.js match js files in path.
  • .{jpg,png,gif} means jpg, png or gif.
  • src/** match all files in src.

How to get the Access Token

When you run cap publish, an Access Token is necessary. If you don't have a publisher, please refer to the Help Document.

After the publisher is created, you could create the corresponding Access Token at Marketplace. Please make sure the publisher in 'package.json' matches the Access Token.

Step 1 - Click Create Token

Step 2 - Enter the name and expired date and submit

Step 3 - Copy and save the Access Token