tentakelfabrik
/
tiny-consent
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2 Commits
1 Branch
18 MiB
Tree: f184cd7e2a
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'f184cd7e2a'
${ noResults }
tiny-consent/node_modules/string_decoder/README.md

47 lines
1.8 KiB
Raw Normal View History

adding
4 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
 
  1. # string_decoder

  2. 

  3. ***Node-core v8.9.4 string_decoder for userland***
  4. 

  5. 

  6. [![NPM](https://nodei.co/npm/string_decoder.png?downloads=true&downloadRank=true)](https://nodei.co/npm/string_decoder/)
  7. [![NPM](https://nodei.co/npm-dl/string_decoder.png?&months=6&height=3)](https://nodei.co/npm/string_decoder/)
  8. 

  9. 

  10. ```bash
  11. npm install --save string_decoder
  12. ```
  13. 

  14. ***Node-core string_decoder for userland***
  15. 

  16. This package is a mirror of the string_decoder implementation in Node-core.
  17. 

  18. Full documentation may be found on the [Node.js website](https://nodejs.org/dist/v8.9.4/docs/api/).
  19. 

  20. As of version 1.0.0 **string_decoder** uses semantic versioning.
  21. 

  22. ## Previous versions

  23. 

  24. Previous version numbers match the versions found in Node core, e.g. 0.10.24 matches Node 0.10.24, likewise 0.11.10 matches Node 0.11.10.
  25. 

  26. ## Update

  27. 

  28. The *build/* directory contains a build script that will scrape the source from the [nodejs/node](https://github.com/nodejs/node) repo given a specific Node version.
  29. 

  30. ## Streams Working Group

  31. 

  32. `string_decoder` is maintained by the Streams Working Group, which
  33. oversees the development and maintenance of the Streams API within
  34. Node.js. The responsibilities of the Streams Working Group include:
  35. 

  36. * Addressing stream issues on the Node.js issue tracker.
  37. * Authoring and editing stream documentation within the Node.js project.
  38. * Reviewing changes to stream subclasses within the Node.js project.
  39. * Redirecting changes to streams from the Node.js project to this
  40.   project.
  41. * Assisting in the implementation of stream providers within Node.js.
  42. * Recommending versions of `readable-stream` to be included in Node.js.
  43. * Messaging about the future of streams to give the community advance
  44.   notice of changes.
  45. 

  46. See [readable-stream](https://github.com/nodejs/readable-stream) for
  47. more details.