hasura/graphql-engine · error

starter kit is not available for framework %s

Error message

starter kit is not available for framework %s

What it means

Validation error: --with-starter-kit was passed to `hasura actions use-codegen`, but the selected framework's entry in the codegen-assets manifest has no starter kit available, so the command refuses to proceed.

Source

Thrown at cli/commands/actions_use_codegen.go:168

		if newCodegenExecutionConfig.Framework == "" {
			return errors.E(op, fmt.Errorf("framework %s is not found", o.framework))
		}
	}

	hasStarterKit := false

	for _, f := range allFrameworks {
		if f.Name == newCodegenExecutionConfig.Framework && f.HasStarterKit {
			hasStarterKit = true
		}
	}

	// if with-starter-kit flag is set and the same is not available for the framework, return error
	if o.withStarterKit && !hasStarterKit {
		return errors.E(
			op,
			fmt.Errorf(
				"starter kit is not available for framework %s",
				newCodegenExecutionConfig.Framework,
			),
		)
	}

	// if with-starter-kit flag is not provided, give an option to clone a starterkit
	if !o.withStarterKit && hasStarterKit {
		shouldCloneStarterKit, err := util.GetYesNoPrompt(
			"Do you also want to clone a starter kit for " + newCodegenExecutionConfig.Framework + "?",
		)
		if err != nil {
			return errors.E(op, fmt.Errorf("error in getting input from user: %w", err))
		}

		o.withStarterKit = shouldCloneStarterKit
	}

View on GitHub (pinned to 724551b9ae)

Solutions

1. Drop the --with-starter-kit flag for frameworks that don't offer one.
2. Pick a framework that ships a starter kit (visible from the prompt list which marks availability).
3. Scaffold the project manually if you need a specific framework plus boilerplate.

Example fix

// before
hasura actions use-codegen --framework <no-kit-framework> --with-starter-kit
// after
hasura actions use-codegen --framework <no-kit-framework>

# check starter kit availability in the clone before passing the flag
find ~/.hasura/codegen-assets -path '*<framework>/starter-kit' -type d | grep -q .

Catch the message, drop --with-starter-kit or switch to a framework that ships a kit, then re-run.

When it happens

Trigger: Choosing a framework whose manifest entry lacks a starter kit directory (hasStarterKit stayed false) while explicitly passing --with-starter-kit.

Common situations: Switching from a framework like nodejs-express (has starter kit) to one without, and keeping the --with-starter-kit flag in a script.

Related errors

• framework %s is not found
• unknown shell: %s. Use bash or zsh
• expected a valid url for --api-host, parsing error: %w
• error in copying starter kit: %w
• cannot validate new config: %w

AI-assisted analysis of hasura/graphql-engine@724551b9ae (2026-08-28). Data as JSON: /api/errors/de4c5e6c87ea89f8. Report an issue: GitHub.