- Moved from NPM to PNPM
- Development environment now is properly hot re-loading
- Support for future plans in regards to mono-repo
- Dependacy updates
Why we released these changes: environment update
This was a crazy release. Altho for the unknown eye, nothing much has changed. You use PNPM package manager instead of NPM, and it looks the same. However, we were hesistant to move to another package manager, as none are really flawless. Even NPM, even PNPM. Turborepo does help a little, but there were some caveats.
The reason it took a while, and jumped from 2.0.2 to 2.0.10, is that there were in-between empty packages. They built fine, packed fine, but when published in the NPM repository, only documentation was left. So we had to remove them. Because of the NPM policy, you cannot overwrite the same package, but they were useless too. So hence the big jump.
In the end, we found out that turborepo’s dependancy was not adhered properly, and it was as simple as taking a look at both the test-setup and the publishing set-up. Apparently, we forgot the build. Locally, we don’t automatically remove it, so it was a false positive. 🤦
Future update
Luckily, it is now properly released, and we will now focus on some improvements that were close to ready. The next updates will be typically boring, and will bring only Gleamy some updates.
We will extract most of the logic to a separate internal package. The reason why we will do this, is to be free of React’s structure. Meaning there will be a more clear input and output that allows us to test better. As well, and this is for the exciting part, helps us in transitioning to a set-up where we can support various platforms like React, Vue, Angular and even vanilla JavaScript, to extend that to stuff like WordPress plugins. Why not? it’s cool! Perhaps, it’s even able to port to a mobile platform without the use of HTML-Canvas…
And not least, we can now bundle all updates to documentation and ship it with each package in the future, and will be always up to date.
And one last thing… one of the most annoying parts is to work separately on the interface to control each Gleamy component, like on the website. We want to ship this as a separate package, inside the monorepo, to allow easier development, and aligment of features. The gleamy website will use the latest versions.
Pretty cool huh!?
Shifting focus
We do need to focus on something other than just development. When promoting Gleamy, we often hear that people really think this project is cool, but not find any use for that. Our other focus, is on getting this right and able to show to the world, other than it’s novelty, an actual useful piece of software this can be.