finish `create-worktop` setup tool
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
> Imported from #129
- [ ] `--cfw` (or `--monorepo` ??) for monorepo/multi-worker setup
_Should use [`cfw`](https://github.com/lukeed/cfw) to build/deploy Workers_
* replaces `wrangler` for deployment (if `--env` is cloudflare)
* replaces `worktop.build` for build system
- [x] `--env` and `--format` combinations
* `--env` – sets the platform/environment target
* default: "cfw" | "cloudflare"
* options: "cfw" | "cloudflare" | "browser" | "deno" | "node"
* `--format` – depends on `--env` value
* `"cfw"` :: "module" (default) | "sw"
* `"browser"` :: "sw" (default)
* `"deno"` :: N/A
* `"node"` :: None (default) | "function" for GCP Functions | "lambda" for AWS lambda family
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the create-worktop setup tool and review the existing --env and --format behavior described in the issue. Determine how the unfinished --cfw or --monorepo option should integrate cfw for multi-worker build and deployment, then verify that the listed environment and format combinations still work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100