npm - @epilot360/icons - Versions diffs - 0.0.2 → 1.0.0 - Mend

@epilot360/icons 0.0.2 → 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (624) hide show

package/iac/node_modules/aws-cdk-lib/node_modules/fs-extra/README.md DELETED Viewed

@@ -1,264 +0,0 @@
-Node.js: fs-extra
-=================
-`fs-extra` adds file system methods that aren't included in the native `fs` module and adds promise support to the `fs` methods. It also uses [`graceful-fs`](https://github.com/isaacs/node-graceful-fs) to prevent `EMFILE` errors. It should be a drop in replacement for `fs`.
-[![npm Package](https://img.shields.io/npm/v/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)
-[![License](https://img.shields.io/npm/l/express.svg)](https://github.com/jprichardson/node-fs-extra/blob/master/LICENSE)
-[![build status](https://img.shields.io/travis/jprichardson/node-fs-extra/master.svg)](http://travis-ci.org/jprichardson/node-fs-extra)
-[![windows Build status](https://img.shields.io/appveyor/ci/jprichardson/node-fs-extra/master.svg?label=windows%20build)](https://ci.appveyor.com/project/jprichardson/node-fs-extra/branch/master)
-[![downloads per month](http://img.shields.io/npm/dm/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)
-[![Coverage Status](https://img.shields.io/coveralls/github/jprichardson/node-fs-extra/master.svg)](https://coveralls.io/github/jprichardson/node-fs-extra)
-[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)
-Why?
-----
-I got tired of including `mkdirp`, `rimraf`, and `ncp` in most of my projects.
-Installation
-------------
-    npm install fs-extra
-Usage
------
-`fs-extra` is a drop in replacement for native `fs`. All methods in `fs` are attached to `fs-extra`. All `fs` methods return promises if the callback isn't passed.
-You don't ever need to include the original `fs` module again:
-```js
-const fs = require('fs') // this is no longer necessary
-```
-you can now do this:
-```js
-const fs = require('fs-extra')
-```
-or if you prefer to make it clear that you're using `fs-extra` and not `fs`, you may want
-to name your `fs` variable `fse` like so:
-```js
-const fse = require('fs-extra')
-```
-you can also keep both, but it's redundant:
-```js
-const fs = require('fs')
-const fse = require('fs-extra')
-```
-Sync vs Async vs Async/Await
--------------
-Most methods are async by default. All async methods will return a promise if the callback isn't passed.
-Sync methods on the other hand will throw if an error occurs.
-Also Async/Await will throw an error if one occurs.
-Example:
-```js
-const fs = require('fs-extra')
-// Async with promises:
-fs.copy('/tmp/myfile', '/tmp/mynewfile')
-  .then(() => console.log('success!'))
-  .catch(err => console.error(err))
-// Async with callbacks:
-fs.copy('/tmp/myfile', '/tmp/mynewfile', err => {
-  if (err) return console.error(err)
-  console.log('success!')
-})
-// Sync:
-try {
-  fs.copySync('/tmp/myfile', '/tmp/mynewfile')
-  console.log('success!')
-} catch (err) {
-  console.error(err)
-}
-// Async/Await:
-async function copyFiles () {
-  try {
-    await fs.copy('/tmp/myfile', '/tmp/mynewfile')
-    console.log('success!')
-  } catch (err) {
-    console.error(err)
-  }
-}
-copyFiles()
-```
-Methods
--------
-### Async
-- [copy](docs/copy.md)
-- [emptyDir](docs/emptyDir.md)
-- [ensureFile](docs/ensureFile.md)
-- [ensureDir](docs/ensureDir.md)
-- [ensureLink](docs/ensureLink.md)
-- [ensureSymlink](docs/ensureSymlink.md)
-- [mkdirp](docs/ensureDir.md)
-- [mkdirs](docs/ensureDir.md)
-- [move](docs/move.md)
-- [outputFile](docs/outputFile.md)
-- [outputJson](docs/outputJson.md)
-- [pathExists](docs/pathExists.md)
-- [readJson](docs/readJson.md)
-- [remove](docs/remove.md)
-- [writeJson](docs/writeJson.md)
-### Sync
-- [copySync](docs/copy-sync.md)
-- [emptyDirSync](docs/emptyDir-sync.md)
-- [ensureFileSync](docs/ensureFile-sync.md)
-- [ensureDirSync](docs/ensureDir-sync.md)
-- [ensureLinkSync](docs/ensureLink-sync.md)
-- [ensureSymlinkSync](docs/ensureSymlink-sync.md)
-- [mkdirpSync](docs/ensureDir-sync.md)
-- [mkdirsSync](docs/ensureDir-sync.md)
-- [moveSync](docs/move-sync.md)
-- [outputFileSync](docs/outputFile-sync.md)
-- [outputJsonSync](docs/outputJson-sync.md)
-- [pathExistsSync](docs/pathExists-sync.md)
-- [readJsonSync](docs/readJson-sync.md)
-- [removeSync](docs/remove-sync.md)
-- [writeJsonSync](docs/writeJson-sync.md)
-**NOTE:** You can still use the native Node.js methods. They are promisified and copied over to `fs-extra`. See [notes on `fs.read()`, `fs.write()`, & `fs.writev()`](docs/fs-read-write-writev.md)
-### What happened to `walk()` and `walkSync()`?
-They were removed from `fs-extra` in v2.0.0. If you need the functionality, `walk` and `walkSync` are available as separate packages, [`klaw`](https://github.com/jprichardson/node-klaw) and [`klaw-sync`](https://github.com/manidlou/node-klaw-sync).
-Third Party
------------
-### CLI
-[fse-cli](https://www.npmjs.com/package/@atao60/fse-cli) allows you to run `fs-extra` from a console or from [npm](https://www.npmjs.com) scripts.
-### TypeScript
-If you like TypeScript, you can use `fs-extra` with it: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fs-extra
-### File / Directory Watching
-If you want to watch for changes to files or directories, then you should use [chokidar](https://github.com/paulmillr/chokidar).
-### Obtain Filesystem (Devices, Partitions) Information
-[fs-filesystem](https://github.com/arthurintelligence/node-fs-filesystem) allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.
-### Misc.
-- [fs-extra-debug](https://github.com/jdxcode/fs-extra-debug) - Send your fs-extra calls to [debug](https://npmjs.org/package/debug).
-- [mfs](https://github.com/cadorn/mfs) - Monitor your fs-extra calls.
-Hacking on fs-extra
--------------------
-Wanna hack on `fs-extra`? Great! Your help is needed! [fs-extra is one of the most depended upon Node.js packages](http://nodei.co/npm/fs-extra.png?downloads=true&downloadRank=true&stars=true). This project
-uses [JavaScript Standard Style](https://github.com/feross/standard) - if the name or style choices bother you,
-you're gonna have to get over it :) If `standard` is good enough for `npm`, it's good enough for `fs-extra`.
-[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)
-What's needed?
-- First, take a look at existing issues. Those are probably going to be where the priority lies.
-- More tests for edge cases. Specifically on different platforms. There can never be enough tests.
-- Improve test coverage. See coveralls output for more info.
-Note: If you make any big changes, **you should definitely file an issue for discussion first.**
-### Running the Test Suite
-fs-extra contains hundreds of tests.
-- `npm run lint`: runs the linter ([standard](http://standardjs.com/))
-- `npm run unit`: runs the unit tests
-- `npm test`: runs both the linter and the tests
-### Windows
-If you run the tests on the Windows and receive a lot of symbolic link `EPERM` permission errors, it's
-because on Windows you need elevated privilege to create symbolic links. You can add this to your Windows's
-account by following the instructions here: http://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7
-However, I didn't have much luck doing this.
-Since I develop on Mac OS X, I use VMWare Fusion for Windows testing. I create a shared folder that I map to a drive on Windows.
-I open the `Node.js command prompt` and run as `Administrator`. I then map the network drive running the following command:
-    net use z: "\\vmware-host\Shared Folders"
-I can then navigate to my `fs-extra` directory and run the tests.
-Naming
-------
-I put a lot of thought into the naming of these functions. Inspired by @coolaj86's request. So he deserves much of the credit for raising the issue. See discussion(s) here:
-* https://github.com/jprichardson/node-fs-extra/issues/2
-* https://github.com/flatiron/utile/issues/11
-* https://github.com/ryanmcgrath/wrench-js/issues/29
-* https://github.com/substack/node-mkdirp/issues/17
-First, I believe that in as many cases as possible, the [Node.js naming schemes](http://nodejs.org/api/fs.html) should be chosen. However, there are problems with the Node.js own naming schemes.
-For example, `fs.readFile()` and `fs.readdir()`: the **F** is capitalized in *File* and the **d** is not capitalized in *dir*. Perhaps a bit pedantic, but they should still be consistent. Also, Node.js has chosen a lot of POSIX naming schemes, which I believe is great. See: `fs.mkdir()`, `fs.rmdir()`, `fs.chown()`, etc.
-We have a dilemma though. How do you consistently name methods that perform the following POSIX commands: `cp`, `cp -r`, `mkdir -p`, and `rm -rf`?
-My perspective: when in doubt, err on the side of simplicity. A directory is just a hierarchical grouping of directories and files. Consider that for a moment. So when you want to copy it or remove it, in most cases you'll want to copy or remove all of its contents. When you want to create a directory, if the directory that it's suppose to be contained in does not exist, then in most cases you'll want to create that too.
-So, if you want to remove a file or a directory regardless of whether it has contents, just call `fs.remove(path)`. If you want to copy a file or a directory whether it has contents, just call `fs.copy(source, destination)`. If you want to create a directory regardless of whether its parent directories exist, just call `fs.mkdirs(path)` or `fs.mkdirp(path)`.
-Credit
-------
-`fs-extra` wouldn't be possible without using the modules from the following authors:
-- [Isaac Shlueter](https://github.com/isaacs)
-- [Charlie McConnel](https://github.com/avianflu)
-- [James Halliday](https://github.com/substack)
-- [Andrew Kelley](https://github.com/andrewrk)
-License
--------
-Licensed under MIT
-Copyright (c) 2011-2017 [JP Richardson](https://github.com/jprichardson)
-[1]: http://nodejs.org/docs/latest/api/fs.html
-[jsonfile]: https://github.com/jprichardson/node-jsonfile

package/iac/node_modules/aws-cdk-lib/node_modules/graceful-fs/LICENSE DELETED Viewed

@@ -1,15 +0,0 @@
-The ISC License
-Copyright (c) 2011-2022 Isaac Z. Schlueter, Ben Noordhuis, and Contributors
-Permission to use, copy, modify, and/or distribute this software for any
-purpose with or without fee is hereby granted, provided that the above
-copyright notice and this permission notice appear in all copies.
-THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
-WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
-ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR
-IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

package/iac/node_modules/aws-cdk-lib/node_modules/graceful-fs/README.md DELETED Viewed

@@ -1,143 +0,0 @@
-# graceful-fs
-graceful-fs functions as a drop-in replacement for the fs module,
-making various improvements.
-The improvements are meant to normalize behavior across different
-platforms and environments, and to make filesystem access more
-resilient to errors.
-## Improvements over [fs module](https://nodejs.org/api/fs.html)
-* Queues up `open` and `readdir` calls, and retries them once
-  something closes if there is an EMFILE error from too many file
-  descriptors.
-* fixes `lchmod` for Node versions prior to 0.6.2.
-* implements `fs.lutimes` if possible. Otherwise it becomes a noop.
-* ignores `EINVAL` and `EPERM` errors in `chown`, `fchown` or
-  `lchown` if the user isn't root.
-* makes `lchmod` and `lchown` become noops, if not available.
-* retries reading a file if `read` results in EAGAIN error.
-On Windows, it retries renaming a file for up to one second if `EACCESS`
-or `EPERM` error occurs, likely because antivirus software has locked
-the directory.
-## USAGE
-```javascript
-// use just like fs
-var fs = require('graceful-fs')
-// now go and do stuff with it...
-fs.readFile('some-file-or-whatever', (err, data) => {
-  // Do stuff here.
-})
-```
-## Sync methods
-This module cannot intercept or handle `EMFILE` or `ENFILE` errors from sync
-methods.  If you use sync methods which open file descriptors then you are
-responsible for dealing with any errors.
-This is a known limitation, not a bug.
-## Global Patching
-If you want to patch the global fs module (or any other fs-like
-module) you can do this:
-```javascript
-// Make sure to read the caveat below.
-var realFs = require('fs')
-var gracefulFs = require('graceful-fs')
-gracefulFs.gracefulify(realFs)
-```
-This should only ever be done at the top-level application layer, in
-order to delay on EMFILE errors from any fs-using dependencies.  You
-should **not** do this in a library, because it can cause unexpected
-delays in other parts of the program.
-## Changes
-This module is fairly stable at this point, and used by a lot of
-things.  That being said, because it implements a subtle behavior
-change in a core part of the node API, even modest changes can be
-extremely breaking, and the versioning is thus biased towards
-bumping the major when in doubt.
-The main change between major versions has been switching between
-providing a fully-patched `fs` module vs monkey-patching the node core
-builtin, and the approach by which a non-monkey-patched `fs` was
-created.
-The goal is to trade `EMFILE` errors for slower fs operations.  So, if
-you try to open a zillion files, rather than crashing, `open`
-operations will be queued up and wait for something else to `close`.
-There are advantages to each approach.  Monkey-patching the fs means
-that no `EMFILE` errors can possibly occur anywhere in your
-application, because everything is using the same core `fs` module,
-which is patched.  However, it can also obviously cause undesirable
-side-effects, especially if the module is loaded multiple times.
-Implementing a separate-but-identical patched `fs` module is more
-surgical (and doesn't run the risk of patching multiple times), but
-also imposes the challenge of keeping in sync with the core module.
-The current approach loads the `fs` module, and then creates a
-lookalike object that has all the same methods, except a few that are
-patched.  It is safe to use in all versions of Node from 0.8 through
-7.0.
-### v4
-* Do not monkey-patch the fs module.  This module may now be used as a
-  drop-in dep, and users can opt into monkey-patching the fs builtin
-  if their app requires it.
-### v3
-* Monkey-patch fs, because the eval approach no longer works on recent
-  node.
-* fixed possible type-error throw if rename fails on windows
-* verify that we *never* get EMFILE errors
-* Ignore ENOSYS from chmod/chown
-* clarify that graceful-fs must be used as a drop-in
-### v2.1.0
-* Use eval rather than monkey-patching fs.
-* readdir: Always sort the results
-* win32: requeue a file if error has an OK status
-### v2.0
-* A return to monkey patching
-* wrap process.cwd
-### v1.1
-* wrap readFile
-* Wrap fs.writeFile.
-* readdir protection
-* Don't clobber the fs builtin
-* Handle fs.read EAGAIN errors by trying again
-* Expose the curOpen counter
-* No-op lchown/lchmod if not implemented
-* fs.rename patch only for win32
-* Patch fs.rename to handle AV software on Windows
-* Close #4 Chown should not fail on einval or eperm if non-root
-* Fix isaacs/fstream#1 Only wrap fs one time
-* Fix #3 Start at 1024 max files, then back off on EMFILE
-* lutimes that doens't blow up on Linux
-* A full on-rewrite using a queue instead of just swallowing the EMFILE error
-* Wrap Read/Write streams as well
-### 1.0
-* Update engines for node 0.6
-* Be lstat-graceful on Windows
-* first