<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Glenn Reyes on Medium]]></title>
        <description><![CDATA[Stories by Glenn Reyes on Medium]]></description>
        <link>https://medium.com/@glennreyes?source=rss-1bf092f8ff4d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*d9DDtcwCDi7PvjeSpQV4nQ.jpeg</url>
            <title>Stories by Glenn Reyes on Medium</title>
            <link>https://medium.com/@glennreyes?source=rss-1bf092f8ff4d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:50:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@glennreyes/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Exploring Kadena.js — Insights into the Kadena Developer’s Experience]]></title>
            <link>https://medium.com/kadena-io/exploring-kadena-js-insights-into-the-kadena-developers-experience-5837a837e3ff?source=rss-1bf092f8ff4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5837a837e3ff</guid>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[pact]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[Glenn Reyes]]></dc:creator>
            <pubDate>Fri, 15 Sep 2023 13:24:53 GMT</pubDate>
            <atom:updated>2023-12-28T19:12:50.338Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Exploring Kadena.js — Insights into the Kadena Developer’s Experience</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FSpTcZA-5Pz-8NXq" /><figcaption>Kadena’s Head of Developer Relations, Glenn Reyes, shares insights into our array of tools built for an exceptional user experience</figcaption></figure><p>Hello Kadenians! If you’ve been following our recent updates (<a href="https://medium.com/kadena-io/kadena-2023-q2-newsletter-a392941a4284"><strong>Kadena Q2 Newsletter</strong></a>,<a href="https://youtu.be/IN8qx_6DgJU"> <strong>Kadena Campfire — Community Call with Randy &amp; Anastasia</strong></a>), you’re already in the loop! Our Developer Experience team has expanded substantially over the past year. With our incredible team of talented developers, we’ve dedicated ourselves to an array of projects geared towards enriching our ecosystem and elevating your experience within it.</p><p>In this article, we’ll walk you through our collective journey within Kadena’s extensive open-source ecosystem. We’ll share insights and experiences from across our team who are actively engaged in different projects. Although we have numerous projects underway, this article will focus on Kadena Client, Chainweb Stream, Kadena Tools, and our new Kadena React UI Components.</p><p>Let’s dive right in!</p><h4>The Kadena Client</h4><p>The <a href="https://github.com/kadena-community/kadena.js/blob/master/packages/libs/client/README.md">Kadena Client</a> is our Javascript/Typescript library that enables users to interact effortlessly with the Kadena Blockchain. This is especially useful for managing accounts and transferring tokens.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cTjcaBJ0qQISAFt23MEYMw.png" /></figure><p>Kadena Client 1.0 is our latest iteration of the JavaScript interface and is an extremely functional and composable API, allowing for increased flexibility and customization for builders and users. Notably, this release also includes WalletConnect as a signing method, based on<a href="https://github.com/kadena-io/KIPs/blob/master/kip-0017.md"> KIP-0017</a>.</p><p>You can learn more about the Kadena Client by checking the <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/libs/client">source code</a>.</p><p>Make sure to check out how you can generate a typesafe client by using the <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/tools/pactjs-cli">@kadena/pactjs-cli</a> that accompanies the <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/libs/client">@kadena/client</a>.</p><h4><strong>Chainweb Stream</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TtpBFbOxE7t1oOA7" /></figure><p>Chainweb Stream plays a crucial role in our ecosystem by providing real-time updates from the Chainweb API. It is instrumental in keeping our applications in sync with the blockchain, particularly for building dynamic applications.</p><p>Click <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/libs/chainweb-stream-client">here</a> to learn how to integrate Chainweb Stream into your applications today!</p><h4>Kadena Tools</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LVaoFVpypwNt2njo" /></figure><p>We’ve been working on a Kadena Tools DApp, which allows users to interact in the Kadena blockchain through several features. This includes generating key pairs, checking for account balance, transferring tokens, the module explorer, managing accounts, and more.</p><p>This project is a work in progress, but if you want to learn more about it, feel free to <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/apps/tools">check out the source code</a>.</p><h4>New Kadena Docs</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*s-vXIU_stFVOsfim" /></figure><p>The Kadena Documentation (Kadena Docs) will be a new resource designed to cover every facet of Kadena, from basic to advanced topics.</p><p>While our current docs include extensive content that might seem overwhelming at first glance, the new Kadena Docs will be meticulously organized, with comprehensive indexing to facilitate a smooth learning process. Whether we’re troubleshooting issues or exploring new features, we hope you will find the new Kadena Docs to be an indispensable resource for new and existing builders! We plan to release our docs around Q4 in 2024!</p><p>Be sure to follow our CXO, <a href="https://twitter.com/Randynamic_4">Randy Daal</a>, on Twitter for exciting updates and sneak peeks!</p><h3>Kadena 🤍 React — New React UI Component Library for Kadena</h3><p>Over the past months, we’ve been working hard building our React UI component library. powered by <a href="https://vanilla-extract.style/">Vanilla Extract</a>. It is based on the unified design system for Kadena.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z09XwxCPbeesz6iu" /></figure><p>The UI component library is specifically created to align the UI of internal Kadena projects. It is also open-sourced and available to the public. From buttons to form elements to primitives to quickly building layouts and pages in no time, the React UI Components are designed to ensure that all applications maintain a uniform look and provide seamless functionality. The main goal of the React UI Components is to make building our internal interfaces effortless so that we can focus on adding unique features for apps on the Kadena blockchain.</p><p>In the future, we plan to build enhanced Kadena blockchain-specific components on top of our primitive UI components with an elevated, familiar user experience.</p><p>The UI component library is still being built, but if you’re curious, you can check out the <a href="https://react-ui.kadena.io/">UI component explorer</a> and the <a href="https://github.com/kadena-community/kadena.js/tree/main/packages/libs/react-ui">source code</a>.</p><h3>Moving forward</h3><p>Our journey in developing the Kadena ecosystem has been a collective one, enriched with unique insights and learning opportunities. We are incredibly proud of our team’s dedication and are also extraordinarily grateful for our community’s feedback and unwavering support. From Chainweb Stream to the React UI Components, each project reflects our commitment to providing an exceptional developer and user experience.</p><p>By sharing our insights, we hope to shed a bit more light on our journey building <a href="https://github.com/kadena-community/kadena.js">kadena.js</a>. Whether you’re a seasoned developer or just getting your feet wet in the world of Web3 development, we invite you to explore our <a href="https://github.com/kadena-community">open-source projects</a> and discover the exciting world of Kadena.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2F9a9e56%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fupscri.be%2F9a9e56&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/78d30e3fd5fc84191dd13999e9cedfc2/href">https://medium.com/media/78d30e3fd5fc84191dd13999e9cedfc2/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5837a837e3ff" width="1" height="1" alt=""><hr><p><a href="https://medium.com/kadena-io/exploring-kadena-js-insights-into-the-kadena-developers-experience-5837a837e3ff">Exploring Kadena.js — Insights into the Kadena Developer’s Experience</a> was originally published in <a href="https://medium.com/kadena-io">Kadena</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to disable Code Splitting in webpack]]></title>
            <link>https://medium.com/@glennreyes/how-to-disable-code-splitting-in-webpack-1c0b1754a3c5?source=rss-1bf092f8ff4d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c0b1754a3c5</guid>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[server-side-rendering]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[code-splitting]]></category>
            <dc:creator><![CDATA[Glenn Reyes]]></dc:creator>
            <pubDate>Sat, 21 Oct 2017 17:55:39 GMT</pubDate>
            <atom:updated>2017-10-27T17:00:39.032Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvvUJ5xQfsu_6nXze5KTXQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/6uBfxz_PTcU">Joana Kosinska</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>With Code Splitting we are able to reduce kilobytes sent over the wire and potentially improve page speed. Code Splitting is a such an easy-to-use feature that every single page app should consider to add (if haven’t yet).</p><h3>So why disable Code Splitting?</h3><p>Well, of course we shouldn’t!</p><p>If you are building server-side rendered apps in React with <a href="https://webpack.js.org/guides/code-splitting/">Code Splitting</a> support baked in, some might use zero-configuration tools like <a href="https://github.com/jaredpalmer/razzle">Razzle</a>, which runs two webpack instances, one for the client and the other for the server, and it builds everything for the client and for the server for you.</p><h4>So let’s just build some app with Code Splitting!</h4><p>After defining some major split points in your app, you want to build and see how the chunks are doing so far:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RUaSpLjHtlil4gC9XS0XRA.png" /></figure><p>And in the file explorer:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/1*wptGHrZQEsikUyz3u4QWdw.png" /></figure><p>But wait?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*XtUp3MIvqfU1kSeUbPADWQ.png" /></figure><h4>What is happening here?</h4><p>Because our app is splitting bundles both on the client and server, multiple bundles are created for the server too, which we don’t really want/need. So we end up having multiple split up <em>[number]</em>.<em>server.js.</em> What we want is:</p><p>📝 One single server.js.</p><h3>Let’s fix it!</h3><p>One way would be to create another build step to delete all [number].server.js, but that would be the last (or not an) option.</p><p>A better way would be to tweak the webpack config to <em>disable Code Splitting for the server</em>. Doing some research I came across<em> </em><a href="https://gist.github.com/jcenturion/892c718abce234243a156255f8f52468">this gist</a> by <a href="https://twitter.com/jcenturion86">@jcenturion86</a> and learned about <a href="https://webpack.js.org/plugins/limit-chunk-count-plugin">LimitChunkCountPlugin</a><em> </em>that allows me to set a limit ofhow many chunks should be created<em>.</em> So the config looks like this:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2e2c7b45eb90233eadcdbc55dd51aa76/href">https://medium.com/media/2e2c7b45eb90233eadcdbc55dd51aa76/href</a></iframe><p>With this, one single chunk/bundle will be created and voila: Code Splitting is disabled.</p><p>So in Razzle, we want to set it only for the server by doing this in the razzle.config.js:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f06655e6ba72f197d0ddd277a7a3ae7d/href">https://medium.com/media/f06655e6ba72f197d0ddd277a7a3ae7d/href</a></iframe><p>Some people encountered type or runtime errors with this approach. So alternatively, we could add these two babel plugins: <a href="https://github.com/airbnb/babel-plugin-dynamic-import-node">babel-plugin-dynamic-import-node</a> to transpile <em>import() </em>to a deferred<em> require() </em>and then remove webpack features with <a href="https://github.com/knpwrs/babel-plugin-remove-webpack">babel-plugin-remove-webpack</a>:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/597c8594ecad342a62d7d198534fc66d/href">https://medium.com/media/597c8594ecad342a62d7d198534fc66d/href</a></iframe><p>Both solutions solve the same issue:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/546/1*Jx-R7wwWw7sRaou1FJOUyA.png" /></figure><p>✅ One single server.js</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c0b1754a3c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>