refactor: Add webawesome and lit as external dependencies

[tbssnch]

Add external peer dependencies to build configuration

Adds @awesome.me/webawesome and lit as external dependencies in the esbuild configuration to prevent bundling them into the library output. This ensures peer dependencies are resolved from the consuming application's node_modules rather than being bundled.

Testing Steps

1. Run a clean build:

rm -rf dist node_modules
pnpm install
pnpm build

• Verify that build completes without errors
• Check that @awesome.me/webawesome and lit are not included in the bundle. (Imports should be preserved)

2. Local consumption test

In the consumer package.json add:

  {
    "dependencies": {
      "@awesome.me/webawesome": "3.0.0-beta.1",
      "@hotosm/ui": "link:../ui",
      "lit": "3.3.1"
    }
  }

Install:

pnpm install

In vite.config.ts add:

  resolve: {
    dedupe: ['@awesome.me/webawesome', 'lit'],
  },

This should only be necessary when testing linking the library locally. This is one of the reasons I think that we should do a staging deploy for additional testing before merging into main.

Start the consumer and verify that the library is working as expected. Open the console and check that errors are no longer showing as before.

Notes: The main changes to the code are the ones in build.js and the package.json. There is a lot of noise after running a build with the changes made.

I did notice some changes included to some of the chunks from the refactor in the last PR that was merged. That is my fault for not running another build after making those changes in the last PR so I went ahead and kept those in there.

[spwoodcock]

Thanks for this suggestion & implementing it!

Sounds like a great way forward to me 😁

Just checking, does lit need to be a peerDep, or can that be a devDep here?

If the consuming app uses the built js, then Lit won't be needed. But I guess if it imports the ts components then it will need Lit installed - is this right? (not ideal, but I guess it can work)