Setup Prisma #
Install a versioned prisma CLI, verify its version, and publish PATH for subsequent pipeline tasks. Implemented in PureScript as a typed Wasm component.
fluentci run setup-prisma setup --version 7.8.0
fluentci run setup-prisma setup --help
Default version: 7.8.0. Override it with an exact compatible npm release using --version. The default stays on the reviewed Prisma ORM 7 CLI rather than the incompatible v8 release candidate on the npm latest tag.
Supported hosts: Linux and macOS on x86_64/aarch64. FreeBSD, OpenBSD and NetBSD fail explicitly before host commands because the upstream Prisma engine distribution does not support these systems. Native engine prerequisites, including compatible OpenSSL libraries on Linux, must be available on the runner.
On Linux/macOS the shared installer ensures Node.js and Bun are available, installs prisma@VERSION with Bun into $HOME/.local/share/fluentci/prisma/VERSION, and links the CLI into that prefix's bin directory. Use an absolute --install-dir to choose a different prefix. Verified existing installations are reused; version mismatches and failed installations do not publish success. Supply a Node version compatible with the selected CLI (Prisma 7.8 requires Node ^20.19, ^22.12 or >=24). Bun's default trusted package list permits Prisma and its engine installation scripts.
Setup does not create or migrate a database and does not install the project's ORM/client or database drivers. Install those using the project's package manager and lockfile. Keep CLI and project dependency versions compatible. Project configuration imports must resolve from that project's own dependencies.
Returns typed tool, version, bin-dir and environment; separate processes must propagate the returned environment. See COMPONENT.md for all options and return descriptions, and the database module for pipeline operations.
Official CLI documentation · MIT license.
Compose this module from code #
Requires FluentCI 0.17.6 or newer for generated pipeline bindings. From your caller module's directory, add the dependency:
fluentci add setup-prisma --path /path/to/fluentci-modules/setup/prisma
For a published module, use fluentci add @fluentci.io/setup-prisma@VERSION with an
available version. Commit the caller's manifest and lockfile. FluentCI generates
named bindings from the installed component's WIT; no handwritten FFI or CLI
subprocess is needed. Include generated source directories in the caller's SDK
project. The callee can use a different SDK from the caller.
Provision prisma before the build steps that require it. The setup result reports the installed version and executable directory.
Replace the sample organization, paths and identifiers with your own. Configure credentials through your CI secret provider before running authenticated operations. Optional arguments use the callee's defaults, and public list fields use comma-separated strings. See COMPONENT.md for argument descriptions and return types.
These examples use the generated composition API and builder chaining in FluentCI 0.17.6; full cross-SDK compilation and execution coverage is still pending. See composition support and limitations.
PureScript #
module Main where
import Prelude
import Effect (Effect)
import FluentCI.Flow as Flow
import FluentCI.Modules.SetupPrisma as SetupPrisma
run :: Effect String
run =
Flow.pipeline "setup-prisma-setup"
# Flow.workdir "."
# SetupPrisma.setup (SetupPrisma.setupArgs)
# Flow.map (\result -> result.version)
# Flow.run
Gleam #
import fluentci/flow
import fluentci_modules/setup_prisma
pub fn run() -> String {
flow.pipeline("setup-prisma-setup")
|> flow.workdir(".")
|> setup_prisma.setup(setup_prisma.setup_args())
|> flow.map(fn(result) { result.version })
|> flow.run
}
Use Gleam's JavaScript target for the Wasm guest. BEAM escripts used for repository automation are separate from component guests.
Elixir #
defmodule Main do
use FluentCI.Plugin
alias FluentCI.Flow
alias FluentCI.Modules.SetupPrisma
defplugin run do
Flow.pipeline("setup-prisma-setup")
|> Flow.workdir(".")
|> SetupPrisma.setup(%{})
|> Flow.stdout()
end
end
Elixir compiles this sequence to Rust/Wasm. Its initial Flow API does not yet provide the typed result callbacks or cleanup combinators of the other examples.
ClojureScript #
(ns main.plugin
(:require [fluentci.flow :as flow]
[fluentci-modules.setup-prisma :as setup_prisma]))
(defn run []
(-> (flow/pipeline "setup-prisma-setup")
(flow/workdir ".")
(setup_prisma/setup {})
flow/run!))
ReScript #
let run = (): string =>
Flow.pipeline("setup-prisma-setup")
->Flow.workdir(".")
->FluentciModulesSetupPrisma.setup(FluentciModulesSetupPrisma.setupArgs)
->Flow.map(result => result.version)
->Flow.run
Python #
from fluentci.flow import pipeline
from fluentci_modules import setup_prisma
def run() -> str:
return (
pipeline("setup-prisma-setup")
.workdir(".")
.pipe(setup_prisma.setup, {})
.map(lambda result: result.version)
.run()
)
TypeScript #
import * as flow from "./fluentci_modules/flow";
import * as setup_prisma from "./fluentci_modules/setup-prisma/index";
export function run(): string {
return flow.pipeline("setup-prisma-setup")
.workdir(".")
.pipe(setup_prisma.setup, {})
.map(result => result.version)
.run();
}
Python and TypeScript use FluentCI builder chains: .pipe(module.function, args)
composes generated module functions with .workdir, .env, and .exec.
Functions return a pipeline carrying their typed result. Use a generated result
callback (With/_with, or a callback argument in TypeScript/Python) when a later
module needs a preceding result; use Flow's map operation to select a result field.
Execution begins at run (or the Elixir plugin terminal), in declared order.
Exported functions #
| Function | Purpose |
|---|---|
setup |
Install and verify prisma, select its version, and publish its environment for subsequent tasks. |