<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: akihito</title>
    <description>The latest articles on DEV Community by akihito (@takihito).</description>
    <link>https://dev.to/takihito</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3893314%2F933f98f6-93d3-4689-ac15-7d726c90af6c.png</url>
      <title>DEV Community: akihito</title>
      <link>https://dev.to/takihito</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/takihito"/>
    <language>en</language>
    <item>
      <title>Lean, Fast, Simple — npm-free GAS Deployment on GitHub Actions with glasp</title>
      <dc:creator>akihito</dc:creator>
      <pubDate>Tue, 12 May 2026 08:56:00 +0000</pubDate>
      <link>https://dev.to/takihito/lean-fast-simple-npm-free-gas-deployment-on-github-actions-with-glasp-3eaj</link>
      <guid>https://dev.to/takihito/lean-fast-simple-npm-free-gas-deployment-on-github-actions-with-glasp-3eaj</guid>
      <description>&lt;p&gt;In the last article, I introduced &lt;strong&gt;glasp&lt;/strong&gt;, a Go-based CLI tool for Google Apps Script (GAS) that operates without a dependency on Node.js.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Previous Article:&lt;/strong&gt; &lt;a href="https://dev.to/takihito/glasp-a-go-based-zero-dependency-cli-for-google-apps-script-clasp-alternative-5hnl"&gt;glasp — A Go-based, zero-dependency CLI for Google Apps Script (clasp Alternative)&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/takihito/glasp" rel="noopener noreferrer"&gt;GitHub Repository: takihito/glasp&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In this post, we will focus on the following:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The benefits of being "npm-independent" in CI/CD environments using GitHub Actions.&lt;/li&gt;
&lt;li&gt;A performance comparison between &lt;code&gt;clasp&lt;/code&gt; and &lt;code&gt;glasp&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  1. "npm-Independence" in GitHub Actions
&lt;/h3&gt;

&lt;p&gt;It is common to see developers using &lt;code&gt;clasp&lt;/code&gt; within GitHub Actions to handle &lt;code&gt;deploy&lt;/code&gt; or &lt;code&gt;push&lt;/code&gt; operations. Typically, the workflow involves these steps:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Setting up the Node.js environment via &lt;code&gt;actions/setup-node&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Installing the tool via &lt;code&gt;npm install -g @google/clasp&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;However, this standard approach presents a few challenges.&lt;/p&gt;

&lt;h4&gt;
  
  
  Reducing Startup Time
&lt;/h4&gt;

&lt;p&gt;&lt;code&gt;npm install&lt;/code&gt; can take anywhere from tens of seconds to several minutes, depending on network conditions and cache status.&lt;br&gt;
&lt;code&gt;glasp&lt;/code&gt;, on the other hand, is a single binary built with Go. It requires neither the Node.js runtime nor the extraction of a massive &lt;code&gt;node_modules&lt;/code&gt; folder. By using the &lt;code&gt;takihito/glasp&lt;/code&gt; action for GitHub Actions, you execute the binary directly, significantly reducing environment setup overhead.&lt;/p&gt;
&lt;h4&gt;
  
  
  Lowering Supply Chain Risk
&lt;/h4&gt;

&lt;p&gt;While the Node.js ecosystem is incredibly powerful, the sheer number of dependency packages increases the risk of vulnerabilities (exposure to supply chain attacks). While multi-functional CLIs like &lt;code&gt;clasp&lt;/code&gt; carry many transitive dependencies, &lt;code&gt;glasp&lt;/code&gt; is provided as a static binary independent of external runtimes. This keeps your CI environment's stability and security much simpler.&lt;/p&gt;


&lt;h3&gt;
  
  
  2. Performance Comparison
&lt;/h3&gt;

&lt;p&gt;I conducted a comparison across several metrics.&lt;/p&gt;
&lt;h4&gt;
  
  
  Lead Time from Setup to Execution
&lt;/h4&gt;

&lt;p&gt;Because &lt;code&gt;glasp&lt;/code&gt; eliminates the need to build a Node.js environment, there is a massive difference in the lead time before execution begins.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;glasp&lt;/th&gt;
&lt;th&gt;clasp&lt;/th&gt;
&lt;th&gt;Speed Ratio (vs clasp)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Setup Time&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;1,337ms&lt;/td&gt;
&lt;td&gt;19,150ms&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;14.3x&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Push Time (Avg)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;1,015ms&lt;/td&gt;
&lt;td&gt;1,229ms&lt;/td&gt;
&lt;td&gt;1.2x&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Pull Time (Avg)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;359ms&lt;/td&gt;
&lt;td&gt;1,270ms&lt;/td&gt;
&lt;td&gt;3.5x&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Total Time&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;2,711ms&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;21,649ms&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;7.9x&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The most significant advantage is the &lt;strong&gt;Setup Time&lt;/strong&gt;. While &lt;code&gt;clasp&lt;/code&gt; requires a global installation via &lt;code&gt;npm install -g @google/clasp&lt;/code&gt; every time (taking roughly 19 seconds), &lt;code&gt;glasp&lt;/code&gt; finishes in about 1.3 seconds just by fetching the pre-compiled single binary. The total cycle of setup → push → pull is &lt;strong&gt;7.9 times faster&lt;/strong&gt;, a benefit that compounds in pipelines with high deployment frequencies.&lt;/p&gt;
&lt;h4&gt;
  
  
  Execution Speed (Push/Pull)
&lt;/h4&gt;

&lt;p&gt;&lt;code&gt;glasp&lt;/code&gt; optimizes file scanning and upload processes through concurrent processing using Goroutines. While the difference might be subtle in small projects, projects with a large number of files or heavy content benefit greatly from Go’s runtime characteristics and optimized I/O.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Reference:&lt;/em&gt; &lt;a href="https://takihito.github.io/glasp/ja/github-actions" rel="noopener noreferrer"&gt;glasp Documentation - GitHub Actions&lt;/a&gt;&lt;/p&gt;


&lt;h3&gt;
  
  
  3. Practical Example: GitHub Actions Configuration
&lt;/h3&gt;

&lt;p&gt;Defining a GitHub Action with &lt;code&gt;glasp&lt;/code&gt; is simple. Just remove the &lt;code&gt;setup-node&lt;/code&gt; step and call the action directly.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy GAS&lt;/span&gt;
&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;push&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt; &lt;span class="nv"&gt;main&lt;/span&gt; &lt;span class="pi"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;deploy&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@v4&lt;/span&gt; &lt;span class="c1"&gt;# Use the latest stable version&lt;/span&gt;

      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;takihito/glasp@v0.2.9&lt;/span&gt;
        &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'&lt;/span&gt;&lt;span class="s"&gt;v0.2.9'&lt;/span&gt;
          &lt;span class="na"&gt;auth&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;${{ secrets.CLASPRC_JSON }}&lt;/span&gt;

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Simply register the contents of your local &lt;code&gt;~/.clasprc.json&lt;/code&gt; as a GitHub Secret named &lt;code&gt;CLASPRC_JSON&lt;/code&gt;, and you are ready to go.&lt;/p&gt;




&lt;h3&gt;
  
  
  4. Conclusion
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;clasp&lt;/code&gt; is the official tool and remains a solid choice for Node.js-centric development environments. However, if you have requirements such as:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Reducing CI execution time&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Removing dependencies on Node.js (npm-independence)&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Building a simple, robust binary-based workflow&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Then I encourage you to give &lt;code&gt;glasp&lt;/code&gt; a try.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Related Links:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://takihito.github.io/glasp/ja/github-actions" rel="noopener noreferrer"&gt;glasp Documentation - GitHub Actions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://github.com/takihito/glasp" rel="noopener noreferrer"&gt;GitHub Repository: takihito/glasp&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>go</category>
      <category>githubactions</category>
      <category>security</category>
      <category>gas</category>
    </item>
    <item>
      <title>glasp: A Go-based, Zero-dependency CLI for Google Apps Script (clasp Alternative)</title>
      <dc:creator>akihito</dc:creator>
      <pubDate>Fri, 24 Apr 2026 05:17:56 +0000</pubDate>
      <link>https://dev.to/takihito/glasp-a-go-based-zero-dependency-cli-for-google-apps-script-clasp-alternative-5hnl</link>
      <guid>https://dev.to/takihito/glasp-a-go-based-zero-dependency-cli-for-google-apps-script-clasp-alternative-5hnl</guid>
      <description>&lt;p&gt;If you use &lt;code&gt;clasp&lt;/code&gt; for local Google Apps Script (GAS) development, you might have faced challenges with Node.js runtime overhead or slow deployment speeds. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/takihito/glasp" rel="noopener noreferrer"&gt;glasp&lt;/a&gt;&lt;/strong&gt; is a Go-based CLI tool designed to address these issues, offering high performance and a simplified developer experience.&lt;/p&gt;




&lt;h3&gt;
  
  
  What is glasp?
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;glasp&lt;/strong&gt; is a CLI for managing Google Apps Script projects. By leveraging Go, it provides a standalone binary that eliminates the need for Node.js while maintaining high compatibility with the official &lt;code&gt;clasp&lt;/code&gt; tool.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Official Site:&lt;/strong&gt; &lt;a href="https://takihito.github.io/glasp/" rel="noopener noreferrer"&gt;https://takihito.github.io/glasp/&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/takihito/glasp" rel="noopener noreferrer"&gt;takihito/glasp&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  Key Features
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Zero Dependencies:&lt;/strong&gt; Runs as a single binary. No Node.js or &lt;code&gt;npm install&lt;/code&gt; required.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;clasp Compatibility:&lt;/strong&gt; Works with existing &lt;code&gt;.clasp.json&lt;/code&gt; and &lt;code&gt;appsscript.json&lt;/code&gt; files. Commands like &lt;code&gt;login&lt;/code&gt;, &lt;code&gt;push&lt;/code&gt;, and &lt;code&gt;pull&lt;/code&gt; follow the same syntax.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;High Performance:&lt;/strong&gt; Concurrent processing allows for significantly faster file scanning and uploading, especially in large projects.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;GitHub Actions Optimized:&lt;/strong&gt; A dedicated Action is available, allowing for deployment without setting up a Node.js environment.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  Installation (Local)
&lt;/h3&gt;

&lt;p&gt;For macOS and Linux, you can install &lt;code&gt;glasp&lt;/code&gt; using the following script:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;curl &lt;span class="nt"&gt;-sL&lt;/span&gt; https://takihito.github.io/glasp/install.sh | bash
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h3&gt;
  
  
  Deployment via GitHub Actions
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;glasp&lt;/code&gt; is provided as a GitHub Action, so you can call it directly in your workflow. This eliminates the "Setup Node.js" step and reduces CI execution time.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy to Google Apps Script&lt;/span&gt;
&lt;span class="na"&gt;on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;push&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;branches&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="pi"&gt;[&lt;/span&gt;&lt;span class="nv"&gt;main&lt;/span&gt;&lt;span class="pi"&gt;]&lt;/span&gt;

&lt;span class="na"&gt;jobs&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;deploy&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;runs-on&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;ubuntu-latest&lt;/span&gt;
    &lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;actions/checkout@v4&lt;/span&gt;

      &lt;span class="pi"&gt;-&lt;/span&gt; &lt;span class="na"&gt;name&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Deploy with glasp&lt;/span&gt;
        &lt;span class="na"&gt;uses&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s"&gt;takihito/glasp@v0.2.8&lt;/span&gt;
        &lt;span class="na"&gt;with&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt;
          &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'&lt;/span&gt;&lt;span class="s"&gt;v0.2.8'&lt;/span&gt;
          &lt;span class="na"&gt;auth&lt;/span&gt;&lt;span class="pi"&gt;:&lt;/span&gt; &lt;span class="s1"&gt;'&lt;/span&gt;&lt;span class="s"&gt;${{&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;secrets.CLASPRC_JSON&lt;/span&gt;&lt;span class="nv"&gt; &lt;/span&gt;&lt;span class="s"&gt;}}'&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Implementation Note:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Register the contents of your local &lt;code&gt;~/.clasprc.json&lt;/code&gt; as a GitHub Secret named &lt;code&gt;CLASPRC_JSON&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Since it runs as a Docker container action, the environment setup is minimal and fast.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  💡 Conclusion
&lt;/h3&gt;

&lt;p&gt;&lt;code&gt;glasp&lt;/code&gt; is a practical alternative for developers who want to decouple their GAS workflow from Node.js or optimize their CI/CD pipelines for speed.&lt;/p&gt;

&lt;p&gt;If you are looking for a lightweight and faster way to manage your scripts while keeping your existing &lt;code&gt;clasp&lt;/code&gt; configurations, &lt;code&gt;glasp&lt;/code&gt; is a strong candidate.&lt;/p&gt;

&lt;h1&gt;
  
  
  googleappsscript #gas #go #githubactions #clasp #glasp
&lt;/h1&gt;

</description>
      <category>cli</category>
      <category>gas</category>
      <category>clasp</category>
      <category>githubactions</category>
    </item>
  </channel>
</rss>
