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
grunt's grunt.file.copy is slightly crippled due to the fact that it does not copy symbolic links but rather resolves them and then copies corresponding file.
For projects using many symlinks this can result in extremely large applications once built , hundreds of MBs for some simple node and html5 apps.
For these reasons, I think we should replace tasks/lib/utils.js:copyFile with a function that supports "copying" symlinks.
The text was updated successfully, but these errors were encountered:
Isn't it intended behaviour to resolve symlimks when copying and packaging an app? Can you give me an example of an symlink that should be preserved instead of being copied?
grunt
'sgrunt.file.copy
is slightly crippled due to the fact that it does not copy symbolic links but rather resolves them and then copies corresponding file.For projects using many symlinks this can result in extremely large applications once built , hundreds of MBs for some simple
node
andhtml5
apps.For these reasons, I think we should replace
tasks/lib/utils.js:copyFile
with a function that supports "copying" symlinks.The text was updated successfully, but these errors were encountered: