ricok/Foundry-VTT-Docker
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Initial

Browse Source
This commit is contained in:
ricok
2025-01-04 00:34:03 +01:00
parent 41829408dc
commit 0ca14bbc19
18111 changed files with 1871397 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

364
resources/app/node_modules/dashdash/CHANGES.md generated vendored Normal file
View File

@@ -0,0 +1,364 @@
# node-dashdash changelog
## not yet released
(nothing yet)
## 1.14.1
- [issue #30] Change the output used by dashdash's Bash completion support to
indicate "there are no completions for this argument" to cope with different
sorting rules on different Bash/platforms. For example:
$ triton -v -p test2 package get <TAB> # before
##-no -tritonpackage- completions-##
$ triton -v -p test2 package get <TAB> # after
##-no-completion- -results-##
## 1.14.0
- New `synopsisFromOpt(<option spec>)` function. This will be used by
[node-cmdln](https://github.com/trentm/node-cmdln) to put together a synopsis
of options for a command. Some examples:
> synopsisFromOpt({names: ['help', 'h'], type: 'bool'});
'[ --help | -h ]'
> synopsisFromOpt({name: 'file', type: 'string', helpArg: 'FILE'});
'[ --file=FILE ]'
## 1.13.1
- [issue #20] `bashCompletionSpecFromOptions` breaks on an options array with
an empty-string group.
## 1.13.0
- Update assert-plus dep to 1.x to get recent fixes (particularly for
`assert.optional*`).
- Drop testing (and official support in packages.json#engines) for node 0.8.x.
Add testing against node 5.x and 4.x with `make testall`.
- [pull #16] Change the `positiveInteger` type to NOT accept zero (0).
For those who might need the old behaviour, see
"examples/custom-option-intGteZero.js". (By Dave Pacheco.)
## 1.12.2
- Bash completion: Add `argtypes` to specify the types of positional args.
E.g. this would allow you to have an `ssh` command with `argtypes = ['host',
'cmd']` for bash completion. You then have to provide Bash functions to
handle completing those types via the `specExtra` arg. See
"[examples/ddcompletion.js](examples/ddcompletion.js)" for an example.
- Bash completion: Tweak so that options or only offered as completions when
there is a leading '-'. E.g. `mytool <TAB>` does NOT offer options, `mytool
-<TAB>` *does*. Without this, a tool with options would never be able to
fallback to Bash's "default" completion. For example `ls <TAB>` wouldn't
result in filename completion. Now it will.
- Bash completion: A workaround for not being able to explicitly have *no*
completion results. Because dashdash's completion uses `complete -o default`,
we fallback to Bash's "default" completion (typically for filename
completion). Before this change, an attempt to explicitly say "there are
no completions that match" would unintentionally trigger filename completion.
Instead as a workaround we return:
$ ddcompletion --none <TAB> # the 'none' argtype
##-no completions-##
$ ddcompletion # a custom 'fruit' argtype
apple banana orange
$ ddcompletion z
##-no -fruit- completions-##
This is a bit of a hack, but IMO a better experience than the surprise
of matching a local filename beginning with 'z', which isn't, in this
case, a "fruit".
## 1.12.1
- Bash completion: Document `<option spec>.completionType`. Add `includeHidden`
option to `bashCompletionSpecFromOptions()`. Add support for dealing with
hidden subcmds.
## 1.12.0
- Support for generating Bash completion files. See the "Bash completion"
section of the README.md and "examples/ddcompletion.js" for an example.
## 1.11.0
- Add the `arrayFlatten` boolean option to `dashdash.addOptionType` used for
custom option types. This allows one to create an `arrayOf...` option type
where each usage of the option can return multiple results. For example:
node mytool.js --foo a,b --foo c
We could define an option type for `--foo` such that
`opts.foo = ['a', 'b', 'c']`. See
"[examples/custom-option-arrayOfCommaSepString.js](examples/custom-option-arrayOfCommaSepString.js)"
for an example.
## 1.10.1
- Trim the published package to the minimal bits. Before: 24K tarball, 144K unpacked.
After: 12K tarball, 48K unpacked. `npm` won't let me drop the README.md. :)
## 1.10.0
- [issue #9] Support `includeDefault` in help config (similar to `includeEnv`) to have a
note of an option's default value, if any, in help output.
- [issue #11] Fix option group breakage introduced in v1.9.0.
## 1.9.0
- [issue #10] Custom option types added with `addOptionType` can specify a
"default" value. See "examples/custom-option-fruit.js".
## 1.8.0
- Support `hidden: true` in an option spec to have help output exclude this
option.
## 1.7.3
- [issue #8] Fix parsing of a short option group when one of the
option takes an argument. For example, consider `tail` with
a `-f` boolean option and a `-n` option that takes a number
argument. This should parse:
tail -fn5
Before this change, that would not parse correctly.
It is suspected that this was introduced in version 1.4.0
(with commit 656fa8bc71c372ebddad0a7026bd71611e2ec99a).
## 1.7.2
- Known issues: #8
- Exclude 'tools/' dir in packages published to npm.
## 1.7.1
- Known issues: #8
- Support an option group *empty string* value:
...
{ group: '' },
...
to render as a blank line in option help. This can help separate loosely
related sets of options without resorting to a title for option groups.
## 1.7.0
- Known issues: #8
- [pull #7] Support for `<parser>.help({helpWrap: false, ...})` option to be able
to fully control the formatting for option help (by Patrick Mooney) `helpWrap:
false` can also be set on individual options in the option objects, e.g.:
var options = [
{
names: ['foo'],
type: 'string',
helpWrap: false,
help: 'long help with\n newlines' +
'\n spaces\n and such\nwill render correctly'
},
...
];
## 1.6.0
- Known issues: #8
- [pull #6] Support headings between groups of options (by Joshua M. Clulow)
so that this code:
var options = [
{ group: 'Armament Options' },
{ names: [ 'weapon', 'w' ], type: 'string' },
{ group: 'General Options' },
{ names: [ 'help', 'h' ], type: 'bool' }
];
...
will give you this help output:
...
Armament Options:
-w, --weapon
General Options:
-h, --help
...
## 1.5.0
- Known issues: #8
- Add support for adding custom option types. "examples/custom-option-duration.js"
shows an example adding a "duration" option type.
$ node custom-option-duration.js -t 1h
duration: 3600000 ms
$ node custom-option-duration.js -t 1s
duration: 1000 ms
$ node custom-option-duration.js -t 5d
duration: 432000000 ms
$ node custom-option-duration.js -t bogus
custom-option-duration.js: error: arg for "-t" is not a valid duration: "bogus"
A custom option type is added via:
var dashdash = require('dashdash');
dashdash.addOptionType({
name: '...',
takesArg: true,
helpArg: '...',
parseArg: function (option, optstr, arg) {
...
}
});
- [issue #4] Add `date` and `arrayOfDate` option types. They accept these date
formats: epoch second times (e.g. 1396031701) and ISO 8601 format:
`YYYY-MM-DD[THH:MM:SS[.sss][Z]]` (e.g. "2014-03-28",
"2014-03-28T18:35:01.489Z"). See "examples/date.js" for an example usage.
$ node examples/date.js -s 2014-01-01 -e $(date +%s)
start at 2014-01-01T00:00:00.000Z
end at 2014-03-29T04:26:18.000Z
## 1.4.0
- Known issues: #8
- [pull #2, pull #3] Add a `allowUnknown: true` option on `createParser` to
allow unknown options to be passed through as `opts._args` instead of parsing
throwing an exception (by https://github.com/isaacs).
See 'allowUnknown' in the README for a subtle caveat.
## 1.3.2
- Fix a subtlety where a *bool* option using both `env` and `default` didn't
work exactly correctly. If `default: false` then all was fine (by luck).
However, if you had an option like this:
options: [ {
names: ['verbose', 'v'],
env: 'FOO_VERBOSE',
'default': true, // <--- this
type: 'bool'
} ],
wanted `FOO_VERBOSE=0` to make the option false, then you need the fix
in this version of dashdash.
## 1.3.1
- [issue #1] Fix an envvar not winning over an option 'default'. Previously
an option with both `default` and `env` would never take a value from the
environment variable. E.g. `FOO_FILE` would never work here:
options: [ {
names: ['file', 'f'],
env: 'FOO_FILE',
'default': 'default.file',
type: 'string'
} ],
## 1.3.0
- [Backward incompatible change for boolean envvars] Change the
interpretation of environment variables for boolean options to consider '0'
to be false. Previous to this *any* value to the envvar was considered
true -- which was quite misleading. Example:
$ FOO_VERBOSE=0 node examples/foo.js
# opts: { verbose: [ false ],
_order: [ { key: 'verbose', value: false, from: 'env' } ],
_args: [] }
# args: []
## 1.2.1
- Fix for `parse.help({includeEnv: true, ...})` handling to ensure that an
option with an `env` **but no `help`** still has the "Environment: ..."
output. E.g.:
{ names: ['foo'], type: 'string', env: 'FOO' }
...
--foo=ARG Environment: FOO=ARG
## 1.2.0
- Transform the option key on the `opts` object returned from
`<parser>.parse()` for convenience. Currently this is just
`s/-/_/g`, e.g. '--dry-run' -> `opts.dry_run`. This allow one to use hyphen
in option names (common) but not have to do silly things like
`opt["dry-run"]` to access the parsed results.
## 1.1.0
- Environment variable integration. Envvars can be associated with an option,
then option processing will fallback to using that envvar if defined and
if the option isn't specified in argv. See the "Environment variable
integration" section in the README.
- Change the `<parser>.parse()` signature to take a single object with keys
for arguments. The old signature is still supported.
- `dashdash.createParser(CONFIG)` alternative to `new dashdash.Parser(CONFIG)`
a la many node-land APIs.
## 1.0.2
- Add "positiveInteger" and "arrayOfPositiveInteger" option types that only
accept positive integers.
- Add "integer" and "arrayOfInteger" option types that accepts only integers.
Note that, for better or worse, these do NOT accept: "0x42" (hex), "1e2"
(with exponent) or "1.", "3.0" (floats).
## 1.0.1
- Fix not modifying the given option spec objects (which breaks creating
a Parser with them more than once).
## 1.0.0
First release.

24
resources/app/node_modules/dashdash/LICENSE.txt generated vendored Normal file
View File

@@ -0,0 +1,24 @@
# This is the MIT license
Copyright (c) 2013 Trent Mick. All rights reserved.
Copyright (c) 2013 Joyent Inc. All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a
copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:
The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

389
resources/app/node_modules/dashdash/etc/dashdash.bash_completion.in generated vendored Normal file
View File

@@ -0,0 +1,389 @@
#!/bin/bash
#
# Bash completion generated for '{{name}}' at {{date}}.
#
# The original template lives here:
# https://github.com/trentm/node-dashdash/blob/master/etc/dashdash.bash_completion.in
#
#
# Copyright 2016 Trent Mick
# Copyright 2016 Joyent, Inc.
#
#
# A generic Bash completion driver script.
#
# This is meant to provide a re-usable chunk of Bash to use for
# "etc/bash_completion.d/" files for individual tools. Only the "Configuration"
# section with tool-specific info need differ. Features:
#
# - support for short and long opts
# - support for knowing which options take arguments
# - support for subcommands (e.g. 'git log <TAB>' to show just options for the
# log subcommand)
# - does the right thing with "--" to stop options
# - custom optarg and arg types for custom completions
# - (TODO) support for shells other than Bash (tcsh, zsh, fish?, etc.)
#
#
# Examples/design:
#
# 1. Bash "default" completion. By default Bash's 'complete -o default' is
# enabled. That means when there are no completions (e.g. if no opts match
# the current word), then you'll get Bash's default completion. Most notably
# that means you get filename completion. E.g.:
# $ tool ./<TAB>
# $ tool READ<TAB>
#
# 2. all opts and subcmds:
# $ tool <TAB>
# $ tool -v <TAB> # assuming '-v' doesn't take an arg
# $ tool -<TAB> # matching opts
# $ git lo<TAB> # matching subcmds
#
# Long opt completions are given *without* the '=', i.e. we prefer space
# separated because that's easier for good completions.
#
# 3. long opt arg with '='
# $ tool --file=<TAB>
# $ tool --file=./d<TAB>
# We maintain the "--file=" prefix. Limitation: With the attached prefix
# the 'complete -o filenames' doesn't know to do dirname '/' suffixing. Meh.
#
# 4. envvars:
# $ tool $<TAB>
# $ tool $P<TAB>
# Limitation: Currently only getting exported vars, so we miss "PS1" and
# others.
#
# 5. Defer to other completion in a subshell:
# $ tool --file $(cat ./<TAB>
# We get this from 'complete -o default ...'.
#
# 6. Custom completion types from a provided bash function.
# $ tool --profile <TAB> # complete available "profiles"
#
#
# Dev Notes:
# - compgen notes, from http://unix.stackexchange.com/questions/151118/understand-compgen-builtin-command
# - https://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html
#
# Debugging this completion:
# 1. Uncomment the "_{{name}}_log_file=..." line.
# 2. 'tail -f /var/tmp/dashdash-completion.log' in one terminal.
# 3. Re-source this bash completion file.
#_{{name}}_log=/var/tmp/dashdash-completion.log
function _{{name}}_completer {
# ---- cmd definition
{{spec}}
# ---- locals
declare -a argv
# ---- support functions
function trace {
[[ -n "$_{{name}}_log" ]] && echo "$*" >&2
}
function _dashdash_complete {
local idx context
idx=$1
context=$2
local shortopts longopts optargs subcmds allsubcmds argtypes
shortopts="$(eval "echo \${cmd${context}_shortopts}")"
longopts="$(eval "echo \${cmd${context}_longopts}")"
optargs="$(eval "echo \${cmd${context}_optargs}")"
subcmds="$(eval "echo \${cmd${context}_subcmds}")"
allsubcmds="$(eval "echo \${cmd${context}_allsubcmds}")"
IFS=', ' read -r -a argtypes <<< "$(eval "echo \${cmd${context}_argtypes}")"
trace ""
trace "_dashdash_complete(idx=$idx, context=$context)"
trace " shortopts: $shortopts"
trace " longopts: $longopts"
trace " optargs: $optargs"
trace " subcmds: $subcmds"
trace " allsubcmds: $allsubcmds"
# Get 'state' of option parsing at this COMP_POINT.
# Copying "dashdash.js#parse()" behaviour here.
local state=
local nargs=0
local i=$idx
local argtype
local optname
local prefix
local word
local dashdashseen=
while [[ $i -lt $len && $i -le $COMP_CWORD ]]; do
argtype=
optname=
prefix=
word=
arg=${argv[$i]}
trace " consider argv[$i]: '$arg'"
if [[ "$arg" == "--" && $i -lt $COMP_CWORD ]]; then
trace " dashdash seen"
dashdashseen=yes
state=arg
word=$arg
elif [[ -z "$dashdashseen" && "${arg:0:2}" == "--" ]]; then
arg=${arg:2}
if [[ "$arg" == *"="* ]]; then
optname=${arg%%=*}
val=${arg##*=}
trace " long opt: optname='$optname' val='$val'"
state=arg
argtype=$(echo "$optargs" | awk -F "-$optname=" '{print $2}' | cut -d' ' -f1)
word=$val
prefix="--$optname="
else
optname=$arg
val=
trace " long opt: optname='$optname'"
state=longopt
word=--$optname
if [[ "$optargs" == *"-$optname="* && $i -lt $COMP_CWORD ]]; then
i=$(( $i + 1 ))
state=arg
argtype=$(echo "$optargs" | awk -F "-$optname=" '{print $2}' | cut -d' ' -f1)
word=${argv[$i]}
trace " takes arg (consume argv[$i], word='$word')"
fi
fi
elif [[ -z "$dashdashseen" && "${arg:0:1}" == "-" ]]; then
trace " short opt group"
state=shortopt
word=$arg
local j=1
while [[ $j -lt ${#arg} ]]; do
optname=${arg:$j:1}
trace " consider index $j: optname '$optname'"
if [[ "$optargs" == *"-$optname="* ]]; then
argtype=$(echo "$optargs" | awk -F "-$optname=" '{print $2}' | cut -d' ' -f1)
if [[ $(( $j + 1 )) -lt ${#arg} ]]; then
state=arg
word=${arg:$(( $j + 1 ))}
trace " takes arg (rest of this arg, word='$word', argtype='$argtype')"
elif [[ $i -lt $COMP_CWORD ]]; then
state=arg
i=$(( $i + 1 ))
word=${argv[$i]}
trace " takes arg (word='$word', argtype='$argtype')"
fi
break
fi
j=$(( $j + 1 ))
done
elif [[ $i -lt $COMP_CWORD && -n "$arg" ]] && $(echo "$allsubcmds" | grep -w "$arg" >/dev/null); then
trace " complete subcmd: recurse _dashdash_complete"
_dashdash_complete $(( $i + 1 )) "${context}__${arg/-/_}"
return
else
trace " not an opt or a complete subcmd"
state=arg
word=$arg
nargs=$(( $nargs + 1 ))
if [[ ${#argtypes[@]} -gt 0 ]]; then
argtype="${argtypes[$(( $nargs - 1 ))]}"
if [[ -z "$argtype" ]]; then
# If we have more args than argtypes, we use the
# last type.
argtype="${argtypes[@]: -1:1}"
fi
fi
fi
trace " state=$state prefix='$prefix' word='$word'"
i=$(( $i + 1 ))
done
trace " parsed: state=$state optname='$optname' argtype='$argtype' prefix='$prefix' word='$word' dashdashseen=$dashdashseen"
local compgen_opts=
if [[ -n "$prefix" ]]; then
compgen_opts="$compgen_opts -P $prefix"
fi
case $state in
shortopt)
compgen $compgen_opts -W "$shortopts $longopts" -- "$word"
;;
longopt)
compgen $compgen_opts -W "$longopts" -- "$word"
;;
arg)
# If we don't know what completion to do, then emit nothing. We
# expect that we are running with:
# complete -o default ...
# where "default" means: "Use Readline's default completion if
# the compspec generates no matches." This gives us the good filename
# completion, completion in subshells/backticks.
#
# We cannot support an argtype="directory" because
# compgen -S '/' -A directory -- "$word"
# doesn't give a satisfying result. It doesn't stop at the trailing '/'
# so you cannot descend into dirs.
if [[ "${word:0:1}" == '$' ]]; then
# By default, Bash will complete '$<TAB>' to all envvars. Apparently
# 'complete -o default' does *not* give us that. The following
# gets *close* to the same completions: '-A export' misses envvars
# like "PS1".
trace " completing envvars"
compgen $compgen_opts -P '$' -A export -- "${word:1}"
elif [[ -z "$argtype" ]]; then
# Only include opts in completions if $word is not empty.
# This is to avoid completing the leading '-', which foils
# using 'default' completion.
if [[ -n "$dashdashseen" ]]; then
trace " completing subcmds, if any (no argtype, dashdash seen)"
compgen $compgen_opts -W "$subcmds" -- "$word"
elif [[ -z "$word" ]]; then
trace " completing subcmds, if any (no argtype, empty word)"
compgen $compgen_opts -W "$subcmds" -- "$word"
else
trace " completing opts & subcmds (no argtype)"
compgen $compgen_opts -W "$shortopts $longopts $subcmds" -- "$word"
fi
elif [[ $argtype == "none" ]]; then
# We want *no* completions, i.e. some way to get the active
# 'complete -o default' to not do filename completion.
trace " completing 'none' (hack to imply no completions)"
echo "##-no-completion- -results-##"
elif [[ $argtype == "file" ]]; then
# 'complete -o default' gives the best filename completion, at least
# on Mac.
trace " completing 'file' (let 'complete -o default' handle it)"
echo ""
elif ! type complete_$argtype 2>/dev/null >/dev/null; then
trace " completing '$argtype' (fallback to default b/c complete_$argtype is unknown)"
echo ""
else
trace " completing custom '$argtype'"
completions=$(complete_$argtype "$word")
if [[ -z "$completions" ]]; then
trace " no custom '$argtype' completions"
# These are in ascii and "dictionary" order so they sort
# correctly.
echo "##-no-completion- -results-##"
else
echo $completions
fi
fi
;;
*)
trace " unknown state: $state"
;;
esac
}
trace ""
trace "-- $(date)"
#trace "\$IFS: '$IFS'"
#trace "\$@: '$@'"
#trace "COMP_WORDBREAKS: '$COMP_WORDBREAKS'"
trace "COMP_CWORD: '$COMP_CWORD'"
trace "COMP_LINE: '$COMP_LINE'"
trace "COMP_POINT: $COMP_POINT"
# Guard against negative COMP_CWORD. This is a Bash bug at least on
# Mac 10.10.4's bash. See
# <https://lists.gnu.org/archive/html/bug-bash/2009-07/msg00125.html>.
if [[ $COMP_CWORD -lt 0 ]]; then
trace "abort on negative COMP_CWORD"
exit 1;
fi
# I don't know how to do array manip on argv vars,
# so copy over to argv array to work on them.
shift # the leading '--'
i=0
len=$#
while [[ $# -gt 0 ]]; do
argv[$i]=$1
shift;
i=$(( $i + 1 ))
done
trace "argv: '${argv[@]}'"
trace "argv[COMP_CWORD-1]: '${argv[$(( $COMP_CWORD - 1 ))]}'"
trace "argv[COMP_CWORD]: '${argv[$COMP_CWORD]}'"
trace "argv len: '$len'"
_dashdash_complete 1 ""
}
# ---- mainline
# Note: This if-block to help work with 'compdef' and 'compctl' is
# adapted from 'npm completion'.
if type complete &>/dev/null; then
function _{{name}}_completion {
local _log_file=/dev/null
[[ -z "$_{{name}}_log" ]] || _log_file="$_{{name}}_log"
COMPREPLY=($(COMP_CWORD="$COMP_CWORD" \
COMP_LINE="$COMP_LINE" \
COMP_POINT="$COMP_POINT" \
_{{name}}_completer -- "${COMP_WORDS[@]}" \
2>$_log_file)) || return $?
}
complete -o default -F _{{name}}_completion {{name}}
elif type compdef &>/dev/null; then
function _{{name}}_completion {
local _log_file=/dev/null
[[ -z "$_{{name}}_log" ]] || _log_file="$_{{name}}_log"
compadd -- $(COMP_CWORD=$((CURRENT-1)) \
COMP_LINE=$BUFFER \
COMP_POINT=0 \
_{{name}}_completer -- "${words[@]}" \
2>$_log_file)
}
compdef _{{name}}_completion {{name}}
elif type compctl &>/dev/null; then
function _{{name}}_completion {
local cword line point words si
read -Ac words
read -cn cword
let cword-=1
read -l line
read -ln point
local _log_file=/dev/null
[[ -z "$_{{name}}_log" ]] || _log_file="$_{{name}}_log"
reply=($(COMP_CWORD="$cword" \
COMP_LINE="$line" \
COMP_POINT="$point" \
_{{name}}_completer -- "${words[@]}" \
2>$_log_file)) || return $?
}
compctl -K _{{name}}_completion {{name}}
fi
##
## This is a Bash completion file for the '{{name}}' command. You can install
## with either:
##
## cp FILE /usr/local/etc/bash_completion.d/{{name}} # Mac
## cp FILE /etc/bash_completion.d/{{name}} # Linux
##
## or:
##
## cp FILE > ~/.{{name}}.completion
## echo "source ~/.{{name}}.completion" >> ~/.bashrc
##

1055
resources/app/node_modules/dashdash/lib/dashdash.js generated vendored Normal file
View File

File diff suppressed because it is too large Load Diff

21
resources/app/node_modules/dashdash/package.json generated vendored Normal file
View File

@@ -0,0 +1,21 @@
{
"name": "dashdash",
"description": "A light, featureful and explicit option parsing library.",
"version": "1.14.1",
"author": "Trent Mick <trentm@gmail.com> (http://trentm.com)",
"repository": {
"type": "git",
"url": "git://github.com/trentm/node-dashdash.git"
},
"main": "./lib/dashdash.js",
"dependencies": {
"assert-plus": "^1.0.0"
},
"devDependencies": {
"nodeunit": "0.9.x"
},
"engines": {
"node": ">=0.10"
},
"license": "MIT"
}