CLI proof of concept

[edahlseng]

This pull request submits the equivalent of the CLI proof of concept I put up at someday-cli PR #1. The same caveats still apply – this is a hacky POC that I'll clean up once we've aligned on the overall approach!

To run the POC, first run ./build.sh, then run node ./packages/cli/dist/cli.js <path-to-config.json>.

I'll copy most of the same notes that I left in the original repo below this line:

---

Hi @rbbydotdev, here's a proof of concept that I put together for us to align on the overall approach for this repository. It's hacky in places and doesn't handle all edge cases, but it proves out the concept. Before I start cleaning it up, please take a look and let me know what you think! A few specific notes and questions:

• Thanks for the tip to use @clack/prompts, it's super easy to use and looks great! I've used commander for parsing arguments.
• The CLI current looks for an optional filepath argument. If one is present, then it will attempt to create a deployment based on the JSON configuration in that file, but if no argument is provided, then the CLI will enter a wizard prompting mode.
• The configuration file is used to store all of the scheduling preferences, and once a new Google Apps Script project is made, the scriptId will be added to the configuration file for reference during future deployments.
• During the cleanup phase for this PR, I'm planning on setting up the Typescript build process for the CLI for consistency.

Screen.Recording.2025-02-16.at.20.51.16.mov

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
someday	❌ Failed (Inspect)			Mar 2, 2025 0:17am