[✨] Create a compiled release

[OulipianSummer]

Is your feature request related to a problem?

I just created a Partytown integration for Drupal (https://www.drupal.org/project/partytown_drupal).

Currently, I'm packaging the compiled Parytown lib directory with the module. However, this isn't an ideal solution. I've got an open issue that suggests using composer to download Partytown as a third party library and place it in a dedicated libraries directory.

However, as far as I'm aware, this would require a npm build step in order to work. Otherwise, composer will just download the source code, which is all written in TypeScript and won't work on the frontend.

Describe the solution you'd like

It would really help integration developers like myself if releases for Partytown included a compiled version of the lib directory so we can follow best practices in the Drupal ecosystem.

Describe alternatives you've considered

Currently, I'm packaging the compiled code by manually running npm install and then extracting the parts I need into my module, but this isn't an ideal solution.

Additional context

No response

[gioboa]

Hi @OulipianSummer 👋 yep, as you mentioned, a possible solution is to add a compiled version of the library in the release note. Ideally this could be automated because otherwise will be an extra work for the team.

[OulipianSummer]

I've opened a draft PR that has about half of this problem figured out. What's missing is a github action that can upload a release asset.

#685