Is clasp still being actively maintained/developed?

[imthenachoman]

If not, is there anything we can do to help keep it going?

[grant]

Hey Nacho Man! Thanks for using clasp. :)

I created clasp and worked on it awhile ago. (not working at the big G anymore). Fun times.

I'll give my (external) perspective~

---

I wouldn't say that this project is actively maintained, but it's definitely not deprecated/archived. The API is still up and running, important PRs for this repo get merged and then the CLI gets auto-published to npm.

If there's something you'd like improved with clasp, I suggest creating a simple, high-quality PR that fixes a filed issue. I did so just a month ago and got a speedy review and merge. #936

[imthenachoman]

I see. Thank you.

I have submitted PRs (#703 and #884) before, value-add ones IMHO, but they just sit there. That's why I thought maybe it was not being maintained.

[MichaelRWolf]

With GitHub's recent move beyond beta and to free accounts for Codespaces (and Copilot), I expect that clasp(1) will be getting a lot more attention. Developing in the browser-based editor is a non-starter for non-trivial coding. It took me an hour of searching last night to find clasp(1). It's been a life-saver.

Perhaps GitHub could do some work to get serious developers onboard GitHub Codespaces, because serious developers don't use non-serious tools. Codespaces is a serious tool, but the editor is not!

[imthenachoman]

Agreed. GAS is the best productivity platform out there -- bar none. I don't think most folks realize how powerful it is. I've been broadcasting it at work and usage has increased exponentially. It solves so many, so, so many business problems.

And with greater usage, clasp is a must. I wouldn't even mind paying for clasp, or GAS for that matter.

[OctanMan]

As a software developer by-day, discovering GAS and clasp has made me feel at home in my attempts to automate some Workspace processes for a non-profit I volunteer at. I only wish its capabilities were more visible - I discovered GAM first which I guess is more in-tune with the sys-admin crowd.

I too am interested to know how much priority Google is giving GAS and clasp. Trying to use the directory_v1 API to set user recovery emails today, I noticed the TS definitions were out of date and didn't include the recoveryEmail property (despite the npm package being updated just 2 months ago) as it's not clear who has responsibility for that now...

The Google API Discovery Service (I'm guessing) didn't exist upon clasps inception, although it now seems like the most low-effort way to keep the TS defs up-to-date using a tool like this: https://github.com/callmehiphop/discovery-tsd googleapis (already a dependency of clasp) to provide the schemas.