I <3 Nuget. But one thing I don't like is that it forces things like JavaScripts to be in one location. I keep my website organized a specific way, and I don't want my scripts in that folder. So it would be nice if certain folders could be configurable to drop items in an alternate location.
Comments: Having mapping info inside packages.config as opposed to nuget.config would allow installing packages from different vendors exactly as you need them. Different package vendors may have different folder structures. For example one package installs scrips to /Scripts root folder another package installs scripts into /Scripts/{Vendor} folder making your overall project structure inconsistent. Instead vendors could just be forced to use /Scripts, /Styles, /Images or /Content folders for their assets and consumers would map these folders to their real-world project structures.
Comments: Having mapping info inside packages.config as opposed to nuget.config would allow installing packages from different vendors exactly as you need them. Different package vendors may have different folder structures. For example one package installs scrips to /Scripts root folder another package installs scripts into /Scripts/{Vendor} folder making your overall project structure inconsistent. Instead vendors could just be forced to use /Scripts, /Styles, /Images or /Content folders for their assets and consumers would map these folders to their real-world project structures.