Kenapa nggunakan modul path tinimbang string concatenation?

Question

Accepted Answer

Modul bawaan **`path`** minangka lan manipulasi file paths **kanthi bener ing saindenge sistem operasi**. Concatenation manual string path nganggo `/` bakal rusak ing Windows (kang nggunakan `\`) lan mishandle edge cases — `path` nangani kabeh kanthi andal.

## Masalah karo string concatenation

```js
// ❌ fragile, OS-dependent, error-prone
const filePath = baseDir + "/" + "sub" + "/" + fileName;
// breaks on Windows (\), doubles slashes if baseDir ends in /, etc.
```

## Perbaikan: path.join

```js
import path from "path";

// ✅ uses the correct separator for the OS, normalizes slashes
const filePath = path.join(baseDir, "sub", fileName);
// Linux/Mac: baseDir/sub/file.txt   Windows: baseDir\sub\file.txt
```

`path.join` nyisipi separator sing bener, ngumpulake duplicate/trailing slashes, lan ngrampung `..`/`.` segments.

## Fungsi path essensial liyane

```js
path.resolve("src", "app.js");  // → ABSOLUTE path from the cwd
path.basename("/a/b/file.txt");  // "file.txt"
path.dirname("/a/b/file.txt");   // "/a/b"
path.extname("file.txt");        // ".txt"
path.parse("/a/b/file.txt");     // { dir, base, name, ext }
path.sep;                         // "/" or "\" depending on OS
```

## Nggoleki direktori file saiki

```js
// CommonJS — built-in globals
const configPath = path.join(__dirname, "config.json");

// ES Modules — __dirname doesn't exist; derive it from import.meta.url
import { fileURLToPath } from "url";
const __dirname = path.dirname(fileURLToPath(import.meta.url));
```

Minangka paths relatif menyang file saiki (karo `__dirname`, utawa ESM equivalent) minangka cara aman kanggo reference files — independent saka endi process dimulai.

## join vs resolve

```text
path.join    → just joins segments (relative stays relative)
path.resolve → produces an ABSOLUTE path (resolves from cwd / right-to-left)
```

## Kenapa iku penting

Nggunakan `path` tinimbang string concatenation nggawe file-handling code **cross-platform lan robust** — sumber bug sing asring kejadian nalika code sing ditulis ing Mac/Linux rusak ing Windows, utawa nalika concatenation ngasilake paths sing malformed.

Inggih minangka kebiasaan cilik karo reliability benefits kang gede, lan ngerti `join` vs `resolve`, tambah carane nggoleki `__dirname` ing ESM, nutup kebutuhan path sehari-hari ing saben Node project kang ngaturi file system.