
<p>Chore</p>



<ul>
<li>Updates dependancies</li>
</ul>



<h2 class="wp-block-heading">Why we released these changes: security updates</h2>



<p>Very boring, but Gleamy needs to stay healthy. This update just brings updates dependancies to ensure secure use.</p>


Gleamy v1.1.8


<p>Bugfixes</p>



<ul>
<li>ESM and CommonJS extensions now have their respective filename extensions (<em>.cjs</em> &amp; <em>.mjs</em>).</li>
</ul>



<h2 class="wp-block-heading">Why we released these changes: “The imported are Next”</h2>



<p>While everything is working perfectly fine with the fixes made in previous versions, there were some annoyances in the state of the previous version. While you can transpile packages, import them relative to the use of webpack/babel to handle many fixes for you, it&#8217;s not a seamless experience when using the Gleamy NPM package. This fix helps ensure that certain environments, such as NextJS, can find the correct settings on their own. The file extensions will assist in selecting the appropriate library type provided in Gleamy.</p>


Gleamy v1.1.7


<p>Bugfixes</p>



<ul>
<li>Solved a bug where export folders are not picked up when installing from NPM.</li>
</ul>



<h2 class="wp-block-heading">Why we released these changes: &#8220;The third one is the charm&#8221;</h2>



<p>In the world of software development, even the tiniest of errors can lead to significant roadblocks. Gleamy, recently released version 1.1.4 and 1.1.5 with the promise of enhancing its features. However, unlike its two predecessors, this patch release, known as Gleamy v1.1.6, turned out to be a fix for an unexpected hiccup. Developers who eagerly installed it via NPM soon found themselves facing an issue that rendered the library unusable. While the two earlier patch releases were intended upgrades, this unexpected error serves as a reminder that even the most meticulously crafted code can have its moments of imperfection. With the huge overhaul of version v1.1.4, there was bound to be an error somewhere. We&#8217;re glad it&#8217;s just this tiny one.</p>


Gleamy v1.1.6


<h2 class="wp-block-heading">Release notes:</h2>



<ul>
<li>Bugfixes
<ul>
<li>Fixed a bug caused by React&#8217;s StrictMode option.</li>
</ul>
</li>
</ul>



<h2 class="wp-block-heading">Why we released these changes</h2>



<p>Twice the Release in a Remarkable Day!</p>



<p>It&#8217;s not every day you witness two releases in a single day, and what an exceptional day it was! Or should we say, what an extraordinary release it turned out to be!</p>



<p>Typically, when a package receives a patch, it implies that someone merely forgot something. However, this time, it was all about the potential unleashed by a brand-new development environment, coupled with a bit of spare time on our hands.</p>



<p>One of the significant challenges that Gleamy faced, particularly when paired with React, was that its performance would steadily decline whenever it underwent rendering or experienced changes in certain props. Adding a single component to a page posed no problems, but when we let our creativity flow – as one should with Gleamy – it simply couldn&#8217;t keep up. This limitation hindered Gleamy&#8217;s ability to expand its use in larger contexts.</p>



<p>Fortunately, we identified the root cause of this issue and promptly resolved it. After an extensive investigation into why altering props adversely affected performance or, in some cases, didn&#8217;t work at all, we uncovered the culprit: two rendering functions persistently running for the same component. Furthermore, changing props exacerbated the problem. To address this, we implemented a fix by unsubscribing the function from the <em>requestAnimationFrame</em> function, allowing JavaScript&#8217;s garbage collection to remove it from the equation.</p>


Gleamy v1.1.5


<h2 class="wp-block-heading">Release notes:</h2>



<ul>
<li>Features
<ul>
<li>Added workspaces to Gleamy&#8217;s main repository</li>



<li>Supplied development environment with NextJS</li>
</ul>
</li>



<li>Bugfixes
<ul>
<li>Server-side-rendering is now supported.
<ul>
<li><em>Note: It obviously still runs on client-side, but it will no longer requires the developer to manually load Gleamy client-side only.</em></li>
</ul>
</li>
</ul>
</li>



<li>Other things
<ul>
<li>Refactored the complete compilation set-up to use: NPM, Rollup, TypeScript, NextJS, ESLint, Prettier and React</li>



<li>Pipeline added for daily NPM package auditing, on top of a weekly Snyk report</li>



<li>Compiled the license-file into the source code</li>



<li>Provided the .md files into npm-tarball</li>
</ul>
</li>
</ul>



<h2 class="wp-block-heading">Why we released these changes</h2>



<p>Greetings! In our previous blog post, titled &#8220;<a href="https://www.gleamy.dev/blog/the-gleamy-chronicles-unveiling-the-enigma-of-our-update-hiatus">The Gleamy Chronicles: Unveiling the Enigma of Our Update Hiatus</a>&#8221; we discussed the factors contributing to Gleamy&#8217;s delayed update. In summary, the features we discussed were in the pipeline and making progress. However, the process of creating these updates has proven to be quite challenging. Tasks such as linking packages, updating the primary website (the component editor), and addressing performance issues have slowed us down. Even after allocating more time to the previously announced update, we concluded that it still wasn&#8217;t up to our standards.±</p>



<p>Furthermore, it has been a hectic few weeks with Bun announcing its all-in-one solution for everything. We gave it a try, and to cut a long story short, it didn&#8217;t align with Gleamy&#8217;s current needs. While it did deliver the promised speed, we thoroughly explored its compatibility with Gleamy.</p>



<p>In the end, instead of relying on tools like Yarn, PNPM, Vite, Webpack, and others, we decided to take a step back and concentrate on what truly mattered:</p>



<ul>
<li>Implementing workspaces to segregate the development environment and future updates.</li>



<li>Focusing on Gleamy and potentially porting it to different platforms.</li>



<li>Creating a robust development environment.</li>



<li>Employing a stable package manager.</li>



<li>Having a clear understanding of how everything is interconnected.</li>
</ul>



<p>This led us to eschew modern tooling that claims to do it all and return to the technologies that initially laid the foundation. We turned to NPM as our package manager, managing workspaces, TypeScript as the compiler, NPM Workspaces (as other package managers required different configurations), Rollup for bundling according to our preferences, ESLint and Prettier for maintaining code style and quality, Jest and React testing library for unit testing. Last but not least, we chose NextJS as the development environment to not only run a web server but also focus on server-side rendering.</p>



<p>We realized that this approach makes the most sense. It served as a reminder that stable technologies, while they may not always boast the speed or features of newer setups, consistently deliver as expected without deviating from community standards. We sometimes forget that they also evolve and improve, rather than merely chasing the latest trends. While new tools are undoubtedly exciting and efficient, they often lead to redundant solutions and increased complexity. As challenging as manually tying everything together can be at times, it maintains transparency. This, in turn, makes it easier to refactor in the future and stay ahead of security concerns.</p>


V1.1.4

Gleamy v1.1.4


<p>Greetings, dear Gleamy enthusiasts! It&#8217;s time to unravel the mystery behind our recent update hiatus and offer you a sneak peek into the intricate world of our development journey. We&#8217;ve been brewing some exciting changes, and we want to share the wizardry that&#8217;s been happening behind the scenes.</p>



<h2 class="wp-block-heading">Why the Wait?</h2>



<p>First and foremost, we&#8217;ve embarked on a quest for performance perfection. Our goal is to provide you with an even more dazzling glitter experience that sparkles like a constellation of stars in the night sky. The low-hanging fruit of improvements has been plucked, and we&#8217;re diving deep into the magical realm of optimizing performance. Creating particles that dance and shine with unparalleled finesse is no easy feat, and we&#8217;re committed to crafting an experience that will leave you spellbound.</p>



<h2 class="wp-block-heading">Introducing the Timer Option</h2>



<p>But wait, there&#8217;s more magic in store! We&#8217;re conjuring a new animation option: the timer. We understand that timers come in all shapes and sizes, and we&#8217;re brewing up a solution that will allow you to create timers outside of our GleamyProvider component, as they are never a generic solution. While this animator option promises to add a touch of enchantment to your designs, we&#8217;re carefully considering how to make it seamlessly usable for wizards of all levels. It&#8217;s like crafting a spell that&#8217;s powerful yet easy to cast! So rather than just adding the timer just to the Gleamy library, we will also create a visual editor for this within Gleamy. And as animators are not yet introduced in the configurator on Gleamy&#8217;s website,&#8230; it&#8217;ll be some work.</p>



<h2 class="wp-block-heading">DPI Scaling Dilemmas</h2>



<p>Ah, the enigma of DPI scaling. While Gleamy currently offers this remarkable feature, we&#8217;re grappling with a conundrum when it comes to screen movement. The pixels should maintain their size, no matter where your screen dances. The challenge lies in the calculation choices that will ensure a harmonious experience, and we&#8217;re diligently working to weave the right spell for pixel perfection.</p>



<h2 class="wp-block-heading">Metal Matters</h2>



<p>And let&#8217;s not forget the captivating world of metallic gradients. Brace yourselves for new additions that will elevate your designs to celestial heights. However, within this realm lies a pivotal decision: should we offer an array of components for every metallic shade, or should we empower you to craft your own magical gradients? It&#8217;s a conundrum that requires the perfect blend of user-friendliness and endless possibilities. We&#8217;re conjuring the perfect solution that will make your metallic dreams come true.</p>



<h2 class="wp-block-heading">The Path Forward</h2>



<p>As you can see, dear readers, our hiatus is not a mere slumber—it&#8217;s a journey of transformation and discovery. We&#8217;re hard at work crafting solutions that will redefine the way you create captivating web experiences with Gleamy. While these core changes may require a bit more time in the cauldron, rest assured that the potion we&#8217;re concocting will be worth the wait.</p>



<p>Stay tuned for updates that will leave you awe-struck and spellbound. Until then, embrace the magic within you and know that we&#8217;re dedicated to crafting a Gleamy experience that&#8217;s truly enchanting.</p>


development

new features

performance

The Gleamy Chronicles: Unveiling the Enigma of Our Update Hiatus


<p><a href="https://www.linkedin.com/feed/update/urn:li:linkedInArticle:7081536944173633537/">Remember that LinkedIn post we shared?</a> Well, we&#8217;ve decided that reaching just a few people wasn&#8217;t enough for the marvelous magic of Gleamy. So, we&#8217;ve added a blog feature to our website! Now, we can share our delightful tales and updates with the whole world. Brace yourselves for a wild ride!</p>







<p>In our latest update, we spruced up the Gleamy website using the enchanting powers of NextJS. We wanted to make sure it&#8217;s not just pretty, but also performs like a superhero on a caffeine high! We&#8217;re fully committed to staying at the forefront of modernization, because who wants to be stuck in the past? Not Gleamy!</p>



<p>Now, let&#8217;s dive into the exhilarating work we&#8217;ve been up to. Picture this: we&#8217;re on a quest to conquer the Window Object Challenge. The absence of the window object on the server-side has thrown some peculiar issues our way. But fear not, dear Gleamy fans, we&#8217;re determined to overcome this obstacle and make Gleamy&#8217;s new version shine brighter than a disco ball at a neon rave! And hey, NextJS may not dance hand-in-hand initially, but we&#8217;re on a mission to create a smoother Gleamy experience, whether it&#8217;s through better loading mechanisms or enhanced documentation.</p>



<p>But wait, there&#8217;s more! Our new website is destined to showcase Gleamy&#8217;s true essence, like a peacock flaunting its mesmerizing feathers. We&#8217;re talking captivating entrances that&#8217;ll make your heart skip a beat. The current homepage is just a sneak peek of the vibrant wonders to come. Soon, we&#8217;ll unveil a spectacle of videos and animated images that&#8217;ll leave you in awe of Gleamy&#8217;s power to create stunning web experiences!</p>



<p>Oh, and did we mention? You can now join our exclusive newsletter. We don&#8217;t write news often, but when we do, we make sure it&#8217;s absolutely awesome! It&#8217;s like receiving a surprise gift from a unicorn in the mail. Trust us, you don&#8217;t want to miss out on this.</p>



<p>Last but certainly not least, feast your eyes on our brand-new blog functionality. Right here, right now, you&#8217;re reading our eccentric musings firsthand. It may not be fully polished just yet (we&#8217;re still adding categories), but hey, why rush when you&#8217;ve got only a few items to showcase? We&#8217;re cooking up exciting ideas – should we keep you updated through the blog for new releases, or create a dedicated release page? The possibilities are as endless as the universe itself, and we&#8217;re excited to explore every glittery corner!</p>



<p>These updates mark an exhilarating milestone for Gleamy as we soar towards technological greatness. The new and improved Gleamy website is on its way, ready to whisk you away into a world of unrivaled Gleamy-foil creation. Stay tuned, because this journey is about to get even more fantastical! ✨</p>


Blog