Working with Paths in BAS

A bot that hardcodes C:\Users\me\bot\data.txt breaks the moment it runs on another machine. The Path module is how you avoid that — building paths dynamically so files resolve correctly wherever the script lives.

Why paths need their own module

A dynamic path is a path to a file or folder that changes depending on its location. You rarely want a fixed absolute path; you want “the data file next to this script” or “the profiles folder inside the project.” Two common cases the module solves: placing browser profiles in the project’s root folder as the bot runs, and figuring out a file’s extension from a path you received.

The actions

Resolving project locations.

• Path to project directory — the folder the project lives in.
• Path to project file — the project file itself.
• Get system path — a known system location.

Build everything relative to these and the bot stays portable.

Constructing and cleaning paths.

• Combine path — join a directory and a name into one valid path, without worrying about slashes.
• Normalise path — clean a path into a canonical form.
• Set path — set the working path.

Inspecting a path.

• Get the file from a path — pull the filename out.
• Get the path from a path — pull the directory out.
• Get file extension — read the extension, e.g. to decide how to process a downloaded file.
• Is the path absolute — check whether a path is absolute or relative before using it.

The habit

Treat hardcoded absolute paths as a bug. Anchor on the project directory, combine to reach your files, and normalise what you build. Do that and the same bot runs unchanged on your machine, a teammate’s, and the VPS you deploy to — which is exactly what you want once a project leaves your desk.