Prerequisites
Before you begin, ensure that your environment meets the following requirements.- You’ll need Node.js 18 or higher installed on your system, along with a package manager such as npm, yarn, or pnpm.
- A valid Fermion API key is required for authentication, which you can obtain from your Fermion Dashboard.
- Familiarity with basic JavaScript or TypeScript will also be helpful as you follow along with the examples in this guide.
Installation
1
Install the Package
Install the package with the help of a package manager of your choice
2
Get Your API Key
Login to your Fermion instructor dashboard and head over to School Setting -> API Access to get your
FERMION_API_KEY. Learn more on how to get your Fermion API key3
Set Up Environment Variables
Create a .env file in your project root and add your API key:
Never commit API keys to version control. Always load them via environment variables or secure secret management systems.
Creating your first Sandbox
Let’s walk through a complete example of creating, running, and cleaning up a sandbox. This example shows how to execute a Node.js script securely in the cloud.Expected Output
The following code snippet will create a sandbox that executes a simple node.js program. Following is the expected output:Common Issues
Error: API key is required
Error: API key is required
This error occurs when your sandbox initialization is missing the
FERMION_API_KEY value.How to fix:- Ensure your
.envfile containsFERMION_API_KEY=your_api_key_here - Verify that your
.envfile is located in your project root - If using
dotenv, import it before creating the sandbox:
Error: Provisioning timeout
Error: Provisioning timeout
This typically means the container took too long to start.Possible fixes:
- Retry after a short delay: the issue may be temporary
- Check the system status page for ongoing service disruptions
- If this persists, contact support with your
snippetIdfor analysis
Error: WebSocket connection failed
Error: WebSocket connection failed
This indicates a network or firewall issue blocking WebSocket traffic.How to fix:
- Ensure
wss://connections are allowed on your network - Check your firewall or proxy configuration
- If using a corporate VPN, try disabling it temporarily
