enhancement/issue 684 improve import map generation diagnostics

[thescientist13]

Related Issue

#684

Documentation

1. docs/issue 144 best practices and recommendations for import maps and referencing node modules www.greenwoodjs.dev#153

Summary of Changes

1. Made diagnostics output a bit more readable

      ****************************************************************************
      - ERROR (ERR_PACKAGE_PATH_NOT_EXPORTED): unable to resolve specifier => `@libsql/core` 
      No "exports" main defined in /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@libsql/core/package.json imported from /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@greenwood/cli/src/lib/walker-package-ranger.js
   
   
   ERROR (ERR_PACKAGE_PATH_NOT_EXPORTED): unable to resolve specifier => @types/ws
   
   No "exports" main defined in /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@types/ws/package.json imported from /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@greenwood/cli/src/lib/walker-package-ranger.js
   
   
   ERROR (ERR_PACKAGE_PATH_NOT_EXPORTED): unable to resolve specifier => dunder-proto
   
   No "exports" main defined in /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/dunder-proto/package.json imported from /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@greenwood/cli/src/lib/walker-package-ranger.js
   
   
   ERROR (ERR_PACKAGE_PATH_NOT_EXPORTED): unable to resolve specifier => math-intrinsics
   
   No "exports" main defined in /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/math-intrinsics/package.json imported from /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@greenwood/cli/src/lib/walker-package-ranger.js
   
   
   ERROR (ERR_MODULE_NOT_FOUND): unable to resolve specifier => type-fest
   
   Cannot find package 'type-fest' imported from /Users/owenbuckley/Workspace/analogstudiosri/api/node_modules/@greenwood/cli/src/lib/walker-package-ranger.js
   
   
   
   
   
   Learn more about these warnings at https://greenwoodjs.dev/docs/introduction/web-standards/#import-maps <<<
   
   
   
   
      

2. Handle NodeJS resolving to built-ins - https://github.com/thescientist13/import-meta-resolve-demo?tab=readme-ov-file#node-built-ins-hijacking-dependencies

TODO

1. Node built ins (expected behavior) - https://github.com/thescientist13/import-meta-resolve-demo?tab=readme-ov-file#node-built-ins-hijacking-dependencies
2. See if we can better handle ERR_PACKAGE_PATH_NOT_EXPORTED - just going to document best we can for now - Improved Import Map Generation Error Handling / Diagnostics reporting #1396
   • https://github.com/thescientist13/import-meta-resolve-demo?tab=readme-ov-file#no-main-exports-map-entry-point-err_package_path_not_exported
   • fails to resolve when specifier is provided to import.meta.resolve es-shims/dunder-proto#3
   • add API for "package dir" nodejs/node#49445 (comment)
3. Make diagnostics a Map
4. final website documentation / takeaways / best practices - docs/issue 144 best practices and recommendations for import maps and referencing node modules www.greenwoodjs.dev#153
5. absorb diagnostics logging output configuration #1394? - Not right now