Closed ayuhito closed 2 months ago
Node 18 nanotar: 0.1.1
createTarGzip([ { name: 'file.txt', data: Buffer.from('Hello, world!'), attrs: { mode: 0o644, mtime: Date.now(), }, } ]).then((tar) => { fs.writeFile('file.tar.gz', tar); })
It doesn't seem like the packed metadata is being included, causing issues in file size reporting on Windows, and mtime for the files are not preserved since there is no way to pass that in.
mtime
No response
Invalid report. I noticed one is a tar while the other is tar+gzip.
tar
tar+gzip
Although it is interesting to note they have the same compression ratio. I wonder if this is actually a bug in tar-fs instead.
tar-fs
Environment
Node 18 nanotar: 0.1.1
Reproduction
Describe the bug
It doesn't seem like the packed metadata is being included, causing issues in file size reporting on Windows, and
mtime
for the files are not preserved since there is no way to pass that in.Additional context
No response
Logs
No response