Open je-die opened 7 years ago
Most likely that's related to nuget cache location (https://github.com/NuGet/Home/issues/3324).
You can check those using: nuget locals all -list
As a workaround when installing locally - you can avoid cache by using:
nuget install Nodejs.Redist.x64 -directdownload
(or dotnet restore --no-cache
)
Speaking of repackaging: the risk of breaking something is too high, I've tried to do it once, but npm failed while resolving one of the dependent packages.
some 'global' workaround: https://github.com/NuGet/Home/issues/1727
Just noticed - Node 10.3.0 with Npm 6.1.0 has flattened dependencies. So the longest path is about 100 characters shorter.
I am trying to use your Nodejs.redist.x64 8.2.0 nuget package on Nuget.org. When I try to install the package, I get this error: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters." It seems to be caused by the nested node_modules folders under the pacote module.
Is there a way you could flatten the npm node modules in the nuget?