JS Import Safety & Runtimes

Import praisonai safely in any JavaScript runtime and migrate from auto-loaded .env

import 'praisonai' runs no process.env reads and no dotenv.config() at load time, so it works in browsers, Electron renderers, webviews (Tauri), and React Native.

Import safety

Importing praisonai no longer touches the runtime environment.

• import 'praisonai' performs no process.env reads and no dotenv.config() at load time — safe in browsers, Electron renderers, webviews (Tauri), and React Native.
• The old dotenv.config() side effect is gone. If you relied on it to auto-load .env in Node, call it yourself (see Migrating from auto-loaded .env).
• The dotenv and node-fetch npm packages are no longer transitive dependencies of praisonai. Both were unused in the SDK source; dropping them improves tree-shaking and shrinks install size.

Do I still need dotenv?

Only .env files need a one-line change; every other credential path is untouched.

Quick Start

1. Zero-config Node with shell env vars

   No code change needed when OPENAI_API_KEY is set in your shell, .zshrc, or systemd unit.

   import { Agent } from 'praisonai';
   
   const agent = new Agent({ instructions: 'You are a helpful assistant' });
   await agent.start('Hello');

2. Node with a .env file

   Load .env yourself — praisonai no longer does it for you.

   import 'dotenv/config';                 // Load .env yourself — praisonai no longer does.
   import { Agent } from 'praisonai';
   
   const agent = new Agent({ instructions: 'You are a helpful assistant' });
   await agent.start('Hello');

3. Browser / webview

   No process, no dotenv, no throw. Pass credentials per-agent.

   import { Agent } from 'praisonai';
   
   // Nothing at module load reaches for `process` or `.env`.
   const agent = new Agent({
     instructions: 'You are a helpful assistant',
     apiKey: import.meta.env.VITE_OPENAI_KEY,
   });
   await agent.chat('Hello from the browser!');

Migrating from auto-loaded .env

praisonai used to call dotenv.config() for you on import — now you call it once yourself.

Process env vars set in the shell, systemd, Docker, or CI still work with zero code changes. Only .env files loaded via the dotenv package need this one-line addition.

// .env was loaded for you the moment you imported the package.
import { Agent } from 'praisonai';
const agent = new Agent({ instructions: 'Hi' });

import 'dotenv/config';       // Load .env explicitly — praisonai no longer does this for you.
import { Agent } from 'praisonai';
const agent = new Agent({ instructions: 'Hi' });

Best Practices

Related