微信小程序云开发商城源码加配置包运行

# cloc  This is just an npm distribution of the amazing [cloc](https://github.com/AlDanial/cloc) by [Al Danial](https://twitter.com/pontifespresso). [I](https://twitter.com/kentcdodds) created this package because I think `cloc` is awesome, but didn't want to download the file and commit it to my project. # Installation and Requirements ## Requirements ### Perl `cloc` is written in perl and the binary that this package exposes is the `cloc` perl script. You must have perl installed on your machine for this binary to work. ### Node & npm This is distributed as an `npm` package (some say that stands for "Node Package Manager"). So you must have Node.js and npm installed. Here are quick instructions on how to get those: http://blog.nodeknockout.com/post/65463770933/how-to-install-node-js-and-npm Congratulations, you've opened your life to a whole new world of awesome tooling and other cool things :-) ## Installation The recommended usage is temporary installation using `npx`: ``` npx cloc [options] ``` However, you can also install it globally or locally to a project. [Learn more](https://flaviocopes.com/npm-packages-local-global/) # Usage In your terminal, simply type `npx cloc` to get output of the options available. See the official [cloc](http://cloc.sourceforge.net/) website for documentation on how to use `cloc`. Here's the output when you run `cloc`: ``` Usage: cloc [options] <file(s)/dir(s)/git hash(es)> | <set 1> <set 2> | <report files> Count, or compute differences of, physical lines of source code in the given files (may be archives such as compressed tarballs or zip files, or git commit hashes or branch names) and/or recursively below the given directories. Input Options --extract-with=<cmd> This option is only needed if cloc is unable to figure out how to extract the contents of the input file(s) by itself. Use <cmd> to extract binary archive files (e.g.: .tar.gz, .zip, .Z). Use the literal '>FILE<' as a stand-in for the actual file(s) to be extracted. For example, to count lines of code in the input files gcc-4.2.tar.gz perl-5.8.8.tar.gz on Unix use --extract-with='gzip -dc >FILE< | tar xf -' or, if you have GNU tar, --extract-with='tar zxf >FILE<' and on Windows use, for example: --extract-with="\"c:\Program Files\WinZip\WinZip32.exe\" -e -o >FILE< ." (if WinZip is installed there). --list-file=<file> Take the list of file and/or directory names to process from <file>, which has one file/directory name per line. Only exact matches are counted; relative path names will be resolved starting from the directory where cloc is invoked. Set <file> to - to read file names from a STDIN pipe. See also --exclude-list-file. --diff-list-file=<file> Take the pairs of file names to be diff'ed from <file>, whose format matches the output of --diff-alignment. (Run with that option to see a sample.) The language identifier at the end of each line is ignored. This enables --diff mode and bypasses file pair alignment logic. --vcs=<VCS> Invoke a system call to <VCS> to obtain a list of files to work on. If <VCS> is 'git', then will invoke 'git ls-files' to get a file list and 'git submodule status' to get a list of submodules whose contents will be ignored. See also --git which accepts git commit hashes and branch names. If <VCS> is 'svn' then will invoke 'svn list -R'. The primary benefit is that cloc will then skip files explicitly excluded by the versioning tool in question, ie, those in .gitignore or have the svn:ignore property. Alternatively <VCS> may be any system command that generates a list of files. Note: cloc must be in a directory which can read the files as they are returned by <VCS>. cloc will not download files from remote repositories. 'svn list -R' may refer to a remote repository to obtain file names (and therefore may require authentication to the remote repository), but the files themselves must be local. Setting <VCS> to 'auto' selects between 'git' and 'svn' (or neither) depending on the presence of a .git or .svn subdirectory below the directory where cloc is invoked. --unicode Check binary files to see if they contain Unicode expanded ASCII text. This causes performance to drop noticeably. Processing Options --autoconf Count .in files (as processed by GNU autoconf) of recognized languages. See also --no-autogen. --by-file Report results for every source file encountered. --by-file-by-lang Report results for every source file encountered in addition to reporting by language. --config <file> Read command line switches from <file> instead of the default location of /Users/kentcdodds/.config/cloc/options.txt. The file should contain one switch, along with arguments (if any), per line. Blank lines and lines beginning with '#' are skipped. Options given on the command line take priority over entries read from the file. --count-and-diff <set1> <set2> First perform direct code counts of source file(s) of <set1> and <set2> separately, then perform a diff of these. Inputs may be pairs of files, directories, or archives. If --out or --report-file is given, three output files will be created, one for each of the two counts and one for the diff. See also --diff, --diff-alignment, --diff-timeout, --ignore-case, --ignore-whitespace. --diff <set1> <set2> Compute differences in code and comments between source file(s) of <set1> and <set2>. The inputs may be any mix of files, directories, archives, or git commit hashes. Use --diff-alignment to generate a list showing which file pairs where compared. When comparing git branches, only files which have changed in either commit are compared. See also --git, --count-and-diff, --di