You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tar-pack does not seem to preserve symlinks created during pack. For example, say node_modules contains symlinks in the directory .bin (which it does),
Expected behavior: node_modules/.bin contains several symlinks, and node_modules2/.bin also contains the same relative symlinks. Actual behavior: node_modules/.bin contains several symlinks, and node_modules2/.binis an empty directory.
Note that un-taring the .tar.gz using tar xvf <filename> causes the symlinks to be preserved correctly.
As far as I can tell there is no flag or option on unpack to configure this behavior, so I suspect this is a bug.
The text was updated successfully, but these errors were encountered:
This is a very misleading comment. Symbolic links are absolutely allowed in packages. Perhaps there is some context I'm missing here? The problem described above is no longer observed after forcing extractOpts.filter to always return true.
tar-pack
does not seem to preserve symlinks created duringpack
. For example, saynode_modules
contains symlinks in the directory.bin
(which it does),Expected behavior:
node_modules/.bin
contains several symlinks, andnode_modules2/.bin
also contains the same relative symlinks.Actual behavior:
node_modules/.bin
contains several symlinks, andnode_modules2/.bin
is an empty directory.Note that un-taring the
.tar.gz
usingtar xvf <filename>
causes the symlinks to be preserved correctly.As far as I can tell there is no flag or option on
unpack
to configure this behavior, so I suspect this is a bug.The text was updated successfully, but these errors were encountered: