web 3d图形渲染器
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.

68 lines
1.7 KiB

  1. # Changelog
  2. ## 6.0
  3. - Drop support for node 6 and 8
  4. - fix symlinks and hardlinks on windows being packed with `\`-style path
  5. targets
  6. ## 5.0
  7. - Address unpack race conditions using path reservations
  8. - Change large-numbers errors from TypeError to Error
  9. - Add `TAR_*` error codes
  10. - Raise `TAR_BAD_ARCHIVE` warning/error when there are no valid entries
  11. found in an archive
  12. - do not treat ignored entries as an invalid archive
  13. - drop support for node v4
  14. - unpack: conditionally use a file mapping to write files on Windows
  15. - Set more portable 'mode' value in portable mode
  16. - Set `portable` gzip option in portable mode
  17. ## 4.4
  18. - Add 'mtime' option to tar creation to force mtime
  19. - unpack: only reuse file fs entries if nlink = 1
  20. - unpack: rename before unlinking files on Windows
  21. - Fix encoding/decoding of base-256 numbers
  22. - Use `stat` instead of `lstat` when checking CWD
  23. - Always provide a callback to fs.close()
  24. ## 4.3
  25. - Add 'transform' unpack option
  26. ## 4.2
  27. - Fail when zlib fails
  28. ## 4.1
  29. - Add noMtime flag for tar creation
  30. ## 4.0
  31. - unpack: raise error if cwd is missing or not a dir
  32. - pack: don't drop dots from dotfiles when prefixing
  33. ## 3.1
  34. - Support `@file.tar` as an entry argument to copy entries from one tar
  35. file to another.
  36. - Add `noPax` option
  37. - `noResume` option for tar.t
  38. - win32: convert `>|<?:` chars to windows-friendly form
  39. - Exclude mtime for dirs in portable mode
  40. ## 3.0
  41. - Minipass-based implementation
  42. - Entirely new API surface, `tar.c()`, `tar.x()` etc., much closer to
  43. system tar semantics
  44. - Massive performance improvement
  45. - Require node 4.x and higher
  46. ## 0.x, 1.x, 2.x - 2011-2014
  47. - fstream-based implementation
  48. - slow and kinda bad, but better than npm shelling out to the system `tar`