Thanks for your feedback! Just a note to let you know that this is absolutely in our roadmap and we are planning to address this request in future. Good to have though also the vote counts, so that we understand the demand around the request, which helps on prioritizing our internal work.Vardhaman Deshpande commented
Also, it would be nice if we got the option to "build a library package" in the yeoman generator.
699 votes17 comments · SharePoint Dev Platform » SharePoint APIs (CSOM/REST/Server-side) · Flag idea as inappropriate… · Admin →
Thank you for your feedback! Just letting you know that we absolutely have this in our backlog, but unfortunately this currently is not included in our short term engineering tasks. We absolutely understand the request and seeing vote counts around this, will help to further prioritize this work for next sprints.Vardhaman Deshpande commented
This needs to be higher. With the SPFx being launched, the only way to work with the managed metadata from an SPFx webpart will be to load JSOM as an external library.
CustomActions that deploy script, JSLinks, and additional web parts on the page are currently not supported in the new experience. Environments that require these unsupported features should continue using classic mode for the time being.
Throughout this year, we will be addressing critical scenario gaps to make the new document library experience support custom processes, commands, and other functionality required for complex, business-critical workflows in complex organizations. Specific capabilities we are investigating building include the ability to host web parts on the page, the ability to define custom view layouts and conditional formatting, and the ability to be visually customized and branded with client-side design pacakages. In the coming weeks we’ll share additional information surrounding these extensibility opportunities across lists and libraries.