Publish release packages to npm registry

[Juanmalopezg]

As discussed in #31 and #36 , this PR adds a GitHub Actions workflow that publishes a new release package to the https://www.npmjs.com/org/moq-js npm repository. This enables distribution via:

npm i @moq-js/player

Note

I tested this behaviour by publishing to https://www.npmjs.com/package/@juanmanulpzg/player. Please check this temp commit in my fork repo to see the only differences compared to the current PR changes.

Considerations:

• The workflow is triggered when a release is published in the https://github.com/englishm/moq-js repository (not on each main branch update).
• Each new release should include an updated version field in package.json.

Feel free to suggest any improvements to these changes ✨

[englishm]

I think 0.1.4 was the last @kixelated/moq release before the fork. I'm thinking maybe we start this at 0.2.0?

[Juanmalopezg]

Sure! Done ✅

[englishm]

After looking into how orgs work on npmjs, I created @moq-js. I was thinking maybe we could then name this package @moq-js/player. How does that sound? Or would @moq-js/moq-player be better?

[Juanmalopezg]

Sounds good, we even discuss this with @JoaquinBCh and @mcintyrehh that we could keep the package name just @moq-js/player by now and try to decouple the inner potential packages like @moq-js/publisher and @moq-js/transport later

[englishm]

For some reason this wasn't sufficient to publish the contents of the dist/ directory - maybe because of how npm only partially overrides .gitignore?

I found that dist/**/* did work though. See the package.json and contents of dist/ here: https://www.npmjs.com/package/@moq-js-ci-test/moq-js?activeTab=code and also https://cdn.jsdelivr.net/npm/@moq-js-ci-test/moq-js@latest/dist/moq-player.iife.js

[Juanmalopezg]

We realize and tested that only the dist folder is needed. I checked locally with npm pack that the dist folder is boundled with "files": ["dist" ] and remove the other folders. You can check https://www.npmjs.com/package/@juanmanulpzg/player/v/0.2.3?activeTab=code .

Hope this fix works for you as well, if not we could try dist/**/*

[englishm]

It's not entirely clear to me what we should have in this top-level package.json for a name and version if we're really only publishing lib/ right now. Should this be kept in sync with lib/package.json or should it be some other placeholder name and version?

[Juanmalopezg]

True. After the changes I fixed on tuesday, I should remove this changes as well. It's done now

[englishm]

This is really great, thank you! Left a few comments about naming/versioning and also one thing we need to fix so the dist/ files get properly published, but otherwise this is looking pretty good! I think we should probably merge the README updates first so the first release is published with proper docs.

[Juanmalopezg]

This is really great, thank you! Left a few comments about naming/versioning and also one thing we need to fix so the dist/ files get properly published, but otherwise this is looking pretty good! I think we should probably merge the README updates first so the first release is published with proper docs.

Thanks for the review! The PR is now updated