# zeronet-fileserver

> ZeroNet fileserver

Latest version **0.0.8** (published 2018-02-25) · MIT license · 0 weekly downloads

## Install

```sh
npm install zeronet-fileserver
pnpm add zeronet-fileserver
yarn add zeronet-fileserver
bun add zeronet-fileserver
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.8 |
| Published | 2018-02-25 |
| First published | 2017-06-25 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 5 |
| Unpacked size | 15.3 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 3 |
| Author | Maciej Krüger |
| Maintainers | mkg20001 |
| Keywords | zeronet, fileserver |

## Links

- npm: https://www.npmjs.com/package/zeronet-fileserver
- Repository: https://github.com/ZeroNetJS/zeronet-fileserver
- Homepage: https://github.com/ZeroNetJS/zeronet-fileserver#readme
- Issues: https://github.com/ZeroNetJS/zeronet-fileserver/issues
- npm.io page: https://npm.io/package/zeronet-fileserver

## Dependencies (5)

- [debug](https://npm.io/package/debug.md) ^3.1.0
- [inet-tools](https://npm.io/package/inet-tools.md) ~0.1.1
- [pull-stream](https://npm.io/package/pull-stream.md) ^3.6.2
- [base32-decode](https://npm.io/package/base32-decode.md) ^1.0.0
- [base32-encode](https://npm.io/package/base32-encode.md) ^1.0.0

## Recent versions

- 0.0.8 (latest) — 2018-02-25
- 0.0.7 — 2017-12-27
- 0.0.6 — 2017-11-25
- 0.0.5 — 2017-11-25
- 0.0.1-alpha18 — 2017-09-10
- 0.0.1-alpha17 — 2017-08-10
- 0.0.1-alpha16 — 2017-08-10
- 0.0.1-alpha15 — 2017-07-22
- 0.0.1-alpha14 — 2017-07-22
- 0.0.1-alpha13 — 2017-07-13
- 0.0.1-alpha12 — 2017-07-07
- 0.0.1-alpha10 — 2017-06-25
- 0.0.1-alpha9 — 2017-06-25

## README

# ZeroNet FileServer
ZeroNet protocol definitions for the fileserver-api

-----

### This module uses `pull-streams`

We expose a streaming interface based on `pull-streams`, rather then on the Node.js core streams implementation (aka Node.js streams). `pull-streams` offers us a better mechanism for error handling and flow control guarantees.

You can learn more about pull-streams at:

- [The history of Node.js streams, nodebp April 2014](https://www.youtube.com/watch?v=g5ewQEuXjsQ)
- [The history of streams, 2016](http://dominictarr.com/post/145135293917/history-of-streams)
- [pull-streams, the simple streaming primitive](http://dominictarr.com/post/149248845122/pull-streams-pull-streams-are-a-very-simple)
- [pull-streams documentation](https://pull-stream.github.io/)

#### Converting `pull-streams` to Node.js Streams

If you are a Node.js streams user, you can convert a pull-stream to a Node.js stream using the module [`pull-stream-to-stream`](https://github.com/pull-stream/pull-stream-to-stream), giving you an instance of a Node.js stream that is linked to the pull-stream. For example:

```js
const pullToStream = require('pull-stream-to-stream')

const nodeStreamInstance = pullToStream(pullStreamInstance)
// nodeStreamInstance is an instance of a Node.js Stream
```

To learn more about this utility, visit https://pull-stream.github.io/#pull-stream-to-stream.

-----

[ZeroNetJS](https://github.com/ZeroNetJS) is developed independently from [ZeroNet](https://github.com/HelloZeroNet)

Docs are autogenerated by [a script](/docs-gen/lib/index.js?raw=true)

---
_Source: https://npm.io/package/zeronet-fileserver · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._