Using FrogBot outside Next.js

​

Run a standalone script

import { getFrogBot } from 'frogbot'
import config from '@frogbot-config'

const seed = async () => {
  const frogbot = await getFrogBot({ config })

  const user = await frogbot.create({
    collection: 'users',
    overrideAccess: true,
    data: {
      email: 'dev@frogbot.com',
      password: 'some-password',
    },
  })

  console.log(`Created user: ${user.email}`)
}

await seed()

pnpm frogbot run src/seed.ts

1. Loads .env* files from the current directory using Next.js environment-loading rules before importing your script. You don’t need dotenv. With NODE_ENV unset, it uses development environment files; set NODE_ENV=production to use production environment files.
2. Resolves the file relative to the current directory and runs TypeScript or JavaScript through tsx, including your app’s @frogbot-config alias.
3. Passes every argument after the file unchanged to your script in process.argv.slice(2). process.argv[1] is the absolute script path.
4. Destroys the cached FrogBot instance and exits with code 0 when your script’s top level finishes. Await all work you need to complete, as in await seed() above; pending timers or background work won’t keep the command running.