Import and export

As a game grows, one giant file gets hard to read. GameSpark lets you split it across files and share code between them with export and import. Add a file with the + in the Files panel.

1. Export from one file

Say you make a file called coin.js with a helper. The export keyword makes it available to other files:

// coin.js
export function drawCoin(x, y) {
  circfill(x, y, 3, 10);        // gold circle
  line(x, y - 2, x, y + 2, 9);  // center line
}

2. Import into another

In main.js, import brings that function in by name, from the file’s path. Then you use it as if it were defined right there:

// main.js
import { drawCoin } from './coin.js';

function draw() {
  cls(1);
  drawCoin(40, 64);
  drawCoin(64, 40);
  drawCoin(88, 64);
}

The { drawCoin } names exactly what you want from the other file, and './coin.js' says which file to get it from.

3. Why split up?

• Tidiness — keep each file focused: enemies in one, the player in another.
• Reuse — a helper you export can be used from several files.
• No name clashes — importing is deliberate, so two files can each have their own x without colliding.

What you learned

• Split a game across files with the + in the Files panel.
• export shares a function or value with other files.
• import { name } from './file.js' brings it in where you need it.
• Modules keep large games organized and prevent accidental name clashes.