clasp | A scheme-like interpreter written in Python | Interpreter library

Why does this clasp command no longer work for me?

clasp run setProperty -p ['domain' 'mydomain.com']

which runs this function

Consider a following simple example, file country.gs

I was wondering how to have different stages (dev. prod) when developing a Google Apps Script webapp. Afaik there is nothing out of the box, especially when you want to have one G Suite Account for dev and another for prod.

The only solution how to handle this, I came up with, is to use Clasp and switch between two GSuite Accounts with clasp logout / login

My questions are:

• Does this work, or are there any reference to one GSuite Account which break when pushing to another account?
• Is there a better approach?

I think it is better to explain it on an example:

I have a Google App Script project setup with clasp on domain test.mydomain.com with the user user@test.mydomain.com

Now I need to push this with clasp to another project (same name) on a different domain prod.mydomain.com. This project is shared with another user where I have the credentials.

The problem is when I now login with the user in clasp I would need to create a project first right? But the project already exists. So how can I handle that?

Why doesn't google Apps Script support latest javascript features like optional chaining even though it's running on Chrome V8? When optional chaining is used, clasp is throwing an error.

GaxiosError: Syntax error: ParseError: Unexpected token .

The runtime environment is already mentioned in the manifest file appsscript.json as:

I use clasp with VS Code to locally developing of Google Apps Script. It's too hard to use default code debugger. So I'm looking for some way to debug code locally. Any suggestions how can I do this?

I have Google Apps Script Project created by "publisher" account and shared as a "view-only":

I want to unit test this code, which is Typescript transpiled using Clasp into Google App Script:

My team is trying to apply modern software engineer techniques in developing an editor add-on for Google Spreadsheet.

With clasp, typescript, jest, git, GCP and CircleCI we were able to achieve:

• local development with our preferred source code management;
• unit testing/tdd on our domain rules;
• manage add-on versions by clasp;
• observability with Stackdriver on GCP;
• with CircleCi, we create a pipeline that executes unit-tests, makes clasp push and versions the add-on with the commit hash as a description.

In addition, through Google Marketplace SDK, the add-on has been distributed privately in our domain, therefore it doesn't need Google approval.

The point is: we're looking for a way to add a step in our pipeline to, programmatically, update and manage our published add-on.

e.g.: after the generation of a new version with clasp, how to put it in the App Configuration on GCP?

gcp app configuration page

In the documentation there are only manual steps.

Thank you all =)

I recently learned about clasp, and became excited about the possibility of using TDD to edit my Google Apps Scripts (GAS) locally.

     NOTE: there might be a way to write tests using the existing GAS editor, but I'd prefer to use a modern editor if at all possible :)

clasp works great, but I cannot figure out how to mock dependencies for unit tests (primarily via jest, though I'm happy to use any tool that works)

• I got farthest by using the gas-local package, and was able to mock a single dependency within a test
  • However I could not find a way to mock multiple dependencies in a single test/call, and so I created this issue

• I am a javascript novice, and probably missed something important while researching this problem :)
• Despite installing @types/google-apps-script, I am unclear on how to "require" or "import" Google Apps Script modules whether using ES5 or ES2015 syntax, respectively--see below for an illustration of this.

Although there is a similar SO question on unit testing here, most of the content/comments appear to be from the pre-clasp era, and I was unable to arrive at a solution while following up the remaining leads. (Granted, it's very possible my untrained eye missed something!).

As I mentioned above, I created an issue (see link above) after trying to mock multiple dependencies while using gas-local. My configuration was similar to the jest.mock test I describe below, though it's worth noting the following differences:

• I used ES5 syntax for the gas-local tests
• My package configuration was probably slightly different