improve documentation around referencing scripts, styles, and import map diagnostics

[thescientist13]

Summary

Coming out of ProjectEvergreen/greenwood#1317 / ProjectEvergreen/greenwood#1326 which did a lot of refactoring around import maps, there were some useful documentation items observed that should be pushed out as part of the next release.

Reference PRs:

• enhancement/issue 1317 import map generation refactor for exports and leveraging import.meta.resolve greenwood#1326
• enhancement/issue 684 import meta resolve refactor part 2 greenwood#1341

Details

1. Import Maps
   • what our import map resolver supports
   • may require hoisting rules from your package manager since default is project directory root
   • understanding diagnostics / known issues with exports and import.meta.resolve
     • @types/trusted-types has an empty main field - https://unpkg.com/browse/@types/[email protected]/package.json
     • geist-font (no default in exports map) - ERR_PACKAGE_PATH_NOT_EXPORTED when package is called using import.meta.resolve vercel/geist-font#150
     • font-awesome (no main or index.js) - https://unpkg.com/browse/[email protected]/package.json
2. best practices regarding using bare specifiers, /node_modules based paths, etc (not needing to know where node_modules are actually located)
3. CSS bundling / node_modules shortcut alias - bug/issue 1346 bundle transitive CSS url(...) references greenwood#1348
4. Plugins
   • resource plugins
     • should only check for extension in the serve lifecycle - https://github.com/ProjectEvergreen/greenwood/pull/1331/files#diff-e20a60e7b88e17250746babe9a6f80b88def96d34e3901541b6ced7dd668b378
     • custom node_modules resolution should handle import maps and use getResolvedHrefFromPathnameShortcut
   • copy plugin
   • theme packs?
5. Add ecosystem demo links to the Lit ecosystem page