Plans for nightly builds

[NanderTGA]

When trying to help someone on msgroom called \u202e yesterday (actually he uses that unicode character as his name, but everyone refers to him by that name because it's an invisible character), I found out it's a pain to get a nightly build from the repository.

The problem

I configured the project in package.json to only include the dist/ folder (the readme, license and package.json are included too by npm). This causes npm to only fetch those things from the repository when telling it to do so. Because of this npm won't download the src/ folder, nor the dist/ folder (it doesn't exist on the repo) and you have to manually clone the repository, rename the cloned folder from msgroom-orm to msgroom and run npm install and npm run build. This is very annoying and I don't want to remove the above setting, because I want to save space.

Solution

I'm working on a new github actions workflow to automatically test and run npm pack on every commit, and to also publish the result at a new package called msgroom-nightly.

The version naming scheme will go as follows:

• Get the current version and only get the coerced contents of it (2.0.0-0 -> 2.0.0)
• Append -(full git sha here) (the dash makes it a prerelease)

This will result in something like this: 2.0.0-ffac537e6cbbf934b08745a378932722df287a53 This won't really work with semantic versioning (even though it's parseable by it), but I don't think it's that much of a problem since it's just a nightly build and use is at your own risk, and you'd have to check manually every time when updating anyway, because every commit could have a breaking change in it.

[NanderTGA]

I should divide everything into seperate workflows because now we got stuff of dependabot trying to get published to npm, which is not very ideal

[NanderTGA]

I fixed the error when unable to publish the nightly build to npm recently. It has been replaced with a warning.