Follow symlinks when creating packages

[winstliu]

I don't see any reason in the code or the blame why lstatSync (which does not follow symlinks) was chosen over statSync (which does). Now create will follow the symlinks and include the destination paths in the package rather than attempting to only include the symlink, which would crash with EISDIR.

Tested this out locally and it works fine - no more EISDIRs, and the Marketplace validated the extension successfully.

Fixes #265

[marcopelegrini]

Please merge this

[polatengin]

thanks, I like it 👍

[PrestonCS]

why is this still not implemented?

[elzik]

I am facing the same issue and would be grateful if this could be merged.

[h45h74x]

Please merge :)

[petero-dk]

This fix also works for making the CLI compatible with projects using PNPM, until it is merged and deployed you can manually fix your locally installed version by

running pnpm list -g tfx-cli --depth=0 to get the installed location

Then opening
_build\exec\extension\init.js and _build\exec\extension\_lib\merger.js

and doing a search and replace for fs.lstat with fs.stat

[symnatbay]

hello? why is this being neglected?

[winstliu]

@tarunramsinghani, could I get some eyes on this? It's been more than a year.