feat: add pnpm and changesets to manage repository

[nmerget]

closes #95

• This PR adds pnpm to manage the creation of all .ts files inside scripts folder with pnpm build
• Removed scripts/out should be build in pipeline or locally to make sure everything is up to date
• Add changesets for release management:
  • Easy Changelog for Open Source projects
  • Detailed descriptions with Markdown
  • Changes the jsb_version.h automatically
• Add CONTRIBUTING.md

[Benjamin-Dobell]

What's the motivation behind uploading and downloading the JS runtime instead of just building it?

I can understand the motivation for v8, since it lives outside of the repository. However, I'm not sure I understand re: the runtime.

Is there potential for race conditions here if multiple builds are kicked off and replace the runtime artifacts?

[nmerget]

It's possible to move the builds for the jsb runtime to a custom action and run it in every OS build. But it reuqires to setup node/pnpm every time. Furthermore, we need to move down to modules/GodotJS/ to run pnpm build.

By moving it to a separate workflow_call we reduce the build time but we have the upload/download stuff.
Another advantage is that you can download the generated files for debugging (only if there are issues in the pipeline).

We can create a custom action instead I don't have a preference

[chucksellick]

Just a comment from personal experience ... pnpm is not significantly better than npm, especially not for a project with so few npm dependencies. And the latest versions of npm have workspace support out of the box. pnpm just means someone might have to install an additional tool to be able to build locally where npm will work fine. (I have also seen significant issues with pnpm and bin paths not working and so on, weird version conflict resolutions that didn't happen with npm, finding myself unable to upgrade pnpm, and probably other stuff)

Unless there is an obvious use case for pnpm that npm can't satisfy, I'd just suggest sticking with npm which any Typescript developer is guaranteed to already have installed.

[nmerget]

Just a comment from personal experience ... pnpm is not significantly better than npm, especially not for a project with so few npm dependencies. And the latest versions of npm have workspace support out of the box. pnpm just means someone might have to install an additional tool to be able to build locally where npm will work fine. (I have also seen significant issues with pnpm and bin paths not working and so on, weird version conflict resolutions that didn't happen with npm, finding myself unable to upgrade pnpm, and probably other stuff)

Unless there is an obvious use case for pnpm that npm can't satisfy, I'd just suggest sticking with npm which any Typescript developer is guaranteed to already have installed.

Personally I like pnpm, but it's totally fine to use npm here. What's your opinion @Benjamin-Dobell?

[Benjamin-Dobell]

Mmm. I tend to avoid these conversations 😅 It's sort of like asking "why use GodotJS when there's already GDScript?"

Personally, I use pnpm for my own projects, so it's what I would have picked. But I'm not tied to it.

That said, I don't think it's accurate to say developers already have npm and don't have pnpm. Package managers themselves have versions, each project will (or at least should) be using a specific version. So a package manager is very likely going to have to be downloaded regardless. Since corepack is bundled in modern Node, it's really no hassle either way.

[chucksellick]

That said, I don't think it's accurate to say developers already have npm and don't have pnpm.

Surely npm is still installed as part of node? You'd have to go to extra lengths to not have it.

[chucksellick]

That said, I don't think it's accurate to say developers already have npm and don't have pnpm. Package managers themselves have versions, each project will (or at least should) be using a specific version. So a package manager is very likely going to have to be downloaded regardless. Since corepack is bundled in modern Node, it's really no hassle either way.

Well it turns out I didn't even know what corepack did :) But it also turns out it's being removed from the distribution in node 25+. https://www.reddit.com/r/node/comments/1jk3vhn/what_are_the_ramifications_of_corepack_being/

[Benjamin-Dobell]

I'm going to have to get used to the new workflow. But I think we should merge this and tweak if we run into problem.