Our package.json syntax permits some fields (specifically 'lib') to contain lists of pathnames, not just a single one. But the recent linker changes I made probably broke the multi-path case, because many of the URI-mapping tools assume that there is just one path in this array. I don't think anyone was using this feature, and it's pretty obscure, so I'd like to remove it. At the very least, I'd like to change the docs to stop claiming that it can tolerate an array, so we aren't teaching users to do something that might not work in the future.
Created attachment 534115 [details] [diff] [review] change docs to stop recommending arrays of paths in package.json