Brunobkr/llama.cpp_AlgMor24_github

1Node.js: fs-extra2=================3 4`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`.5 6[![npm Package](https://img.shields.io/npm/v/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)7[![License](https://img.shields.io/npm/l/express.svg)](https://github.com/jprichardson/node-fs-extra/blob/master/LICENSE)8[![build status](https://img.shields.io/travis/jprichardson/node-fs-extra/master.svg)](http://travis-ci.org/jprichardson/node-fs-extra)9[![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)10[![downloads per month](http://img.shields.io/npm/dm/fs-extra.svg)](https://www.npmjs.org/package/fs-extra)11[![Coverage Status](https://img.shields.io/coveralls/github/jprichardson/node-fs-extra/master.svg)](https://coveralls.io/github/jprichardson/node-fs-extra)12[![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)13 14Why?15----16 17I got tired of including `mkdirp`, `rimraf`, and `ncp` in most of my projects.18 19 20 21 22Installation23------------24 25    npm install fs-extra26 27 28 29Usage30-----31 32`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.33 34You don't ever need to include the original `fs` module again:35 36```js37const fs = require('fs') // this is no longer necessary38```39 40you can now do this:41 42```js43const fs = require('fs-extra')44```45 46or if you prefer to make it clear that you're using `fs-extra` and not `fs`, you may want47to name your `fs` variable `fse` like so:48 49```js50const fse = require('fs-extra')51```52 53you can also keep both, but it's redundant:54 55```js56const fs = require('fs')57const fse = require('fs-extra')58```59 60Sync vs Async vs Async/Await61-------------62Most methods are async by default. All async methods will return a promise if the callback isn't passed.63 64Sync methods on the other hand will throw if an error occurs.65 66Also Async/Await will throw an error if one occurs.67 68Example:69 70```js71const fs = require('fs-extra')72 73// Async with promises:74fs.copy('/tmp/myfile', '/tmp/mynewfile')75  .then(() => console.log('success!'))76  .catch(err => console.error(err))77 78// Async with callbacks:79fs.copy('/tmp/myfile', '/tmp/mynewfile', err => {80  if (err) return console.error(err)81  console.log('success!')82})83 84// Sync:85try {86  fs.copySync('/tmp/myfile', '/tmp/mynewfile')87  console.log('success!')88} catch (err) {89  console.error(err)90}91 92// Async/Await:93async function copyFiles () {94  try {95    await fs.copy('/tmp/myfile', '/tmp/mynewfile')96    console.log('success!')97  } catch (err) {98    console.error(err)99  }100}101 102copyFiles()103```104 105 106Methods107-------108 109### Async110 111- [copy](docs/copy.md)112- [emptyDir](docs/emptyDir.md)113- [ensureFile](docs/ensureFile.md)114- [ensureDir](docs/ensureDir.md)115- [ensureLink](docs/ensureLink.md)116- [ensureSymlink](docs/ensureSymlink.md)117- [mkdirp](docs/ensureDir.md)118- [mkdirs](docs/ensureDir.md)119- [move](docs/move.md)120- [outputFile](docs/outputFile.md)121- [outputJson](docs/outputJson.md)122- [pathExists](docs/pathExists.md)123- [readJson](docs/readJson.md)124- [remove](docs/remove.md)125- [writeJson](docs/writeJson.md)126 127### Sync128 129- [copySync](docs/copy-sync.md)130- [emptyDirSync](docs/emptyDir-sync.md)131- [ensureFileSync](docs/ensureFile-sync.md)132- [ensureDirSync](docs/ensureDir-sync.md)133- [ensureLinkSync](docs/ensureLink-sync.md)134- [ensureSymlinkSync](docs/ensureSymlink-sync.md)135- [mkdirpSync](docs/ensureDir-sync.md)136- [mkdirsSync](docs/ensureDir-sync.md)137- [moveSync](docs/move-sync.md)138- [outputFileSync](docs/outputFile-sync.md)139- [outputJsonSync](docs/outputJson-sync.md)140- [pathExistsSync](docs/pathExists-sync.md)141- [readJsonSync](docs/readJson-sync.md)142- [removeSync](docs/remove-sync.md)143- [writeJsonSync](docs/writeJson-sync.md)144 145 146**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)147 148### What happened to `walk()` and `walkSync()`?149 150They 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).151 152 153Third Party154-----------155 156### CLI157 158[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.159 160### TypeScript161 162If you like TypeScript, you can use `fs-extra` with it: https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/fs-extra163 164 165### File / Directory Watching166 167If you want to watch for changes to files or directories, then you should use [chokidar](https://github.com/paulmillr/chokidar).168 169### Obtain Filesystem (Devices, Partitions) Information170 171[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.172 173### Misc.174 175- [fs-extra-debug](https://github.com/jdxcode/fs-extra-debug) - Send your fs-extra calls to [debug](https://npmjs.org/package/debug).176- [mfs](https://github.com/cadorn/mfs) - Monitor your fs-extra calls.177 178 179 180Hacking on fs-extra181-------------------182 183Wanna 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 project184uses [JavaScript Standard Style](https://github.com/feross/standard) - if the name or style choices bother you,185you're gonna have to get over it :) If `standard` is good enough for `npm`, it's good enough for `fs-extra`.186 187[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)188 189What's needed?190- First, take a look at existing issues. Those are probably going to be where the priority lies.191- More tests for edge cases. Specifically on different platforms. There can never be enough tests.192- Improve test coverage. See coveralls output for more info.193 194Note: If you make any big changes, **you should definitely file an issue for discussion first.**195 196### Running the Test Suite197 198fs-extra contains hundreds of tests.199 200- `npm run lint`: runs the linter ([standard](http://standardjs.com/))201- `npm run unit`: runs the unit tests202- `npm test`: runs both the linter and the tests203 204 205### Windows206 207If you run the tests on the Windows and receive a lot of symbolic link `EPERM` permission errors, it's208because on Windows you need elevated privilege to create symbolic links. You can add this to your Windows's209account by following the instructions here: http://superuser.com/questions/104845/permission-to-make-symbolic-links-in-windows-7210However, I didn't have much luck doing this.211 212Since 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.213I open the `Node.js command prompt` and run as `Administrator`. I then map the network drive running the following command:214 215    net use z: "\\vmware-host\Shared Folders"216 217I can then navigate to my `fs-extra` directory and run the tests.218 219 220Naming221------222 223I 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:224 225* https://github.com/jprichardson/node-fs-extra/issues/2226* https://github.com/flatiron/utile/issues/11227* https://github.com/ryanmcgrath/wrench-js/issues/29228* https://github.com/substack/node-mkdirp/issues/17229 230First, 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.231 232For 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.233 234We have a dilemma though. How do you consistently name methods that perform the following POSIX commands: `cp`, `cp -r`, `mkdir -p`, and `rm -rf`?235 236My 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.237 238So, 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)`.239 240 241Credit242------243 244`fs-extra` wouldn't be possible without using the modules from the following authors:245 246- [Isaac Shlueter](https://github.com/isaacs)247- [Charlie McConnel](https://github.com/avianflu)248- [James Halliday](https://github.com/substack)249- [Andrew Kelley](https://github.com/andrewrk)250 251 252 253 254License255-------256 257Licensed under MIT258 259Copyright (c) 2011-2017 [JP Richardson](https://github.com/jprichardson)260 261[1]: http://nodejs.org/docs/latest/api/fs.html262 263 264[jsonfile]: https://github.com/jprichardson/node-jsonfile265