fix(loader): resolve --config relative paths against cwd, not shipnode's dist/

`shipnode deploy --config ./shipnode.frontend.config.ts` threw
`Cannot find module` because jiti's anchor is shipnode's own loader file
inside dist/, so relative paths resolved there instead of against the
user's working directory. Affected anyone with per-app configs in a
monorepo. Absolute paths kept working and stay unchanged (`resolve()`
returns absolute paths verbatim).

Also moves the 2.5.0 content out of [Unreleased] now that it's tagged.

Author: devalade

CHANGELOG.md

@@ -4,6 +4,11 @@ All notable changes to `@devalade/shipnode` will be documented here.
 
 ## [Unreleased]
 
+### Fixed
+- **`--config <relative-path>` now resolves against the user's cwd, not against shipnode's install dir.** Previously `shipnode deploy --config ./shipnode.frontend.config.ts` threw `Cannot find module './shipnode.frontend.config.ts'` because jiti's anchor is shipnode's own loader file inside `dist/`. Affected anyone using per-app configs in monorepos. Absolute paths kept working and are unchanged.
+
+## [2.5.0] - 2026-05-28
+
 ### Fixed
 - **Env vars now actually reach the app under PM2 7.x.** PM2's `env_file` option silently failed to inject variables in 7.0.x, so AdonisJS / NestJS / any framework that re-validates env at boot crashed with "Missing environment variable" after deploy. Each PM2 app is now started as `bash -c "set -a && . <shared-env> && set +a && exec <original-command>"`; the `env_file` line is gone from the generated ecosystem. Secrets stay in the chmod-600 shared env file — they're not duplicated into `ecosystem.config.cjs`. See [ADR-0003](docs/adr/0003-source-env-instead-of-pm2-env-file.md).
 - **`shipnode env` upload now matches the PM2 ecosystem reference.** Upload was hardcoded to `shared/.env`, while the ecosystem referenced `shared/${envFile}`. If you set `.envFile('.env.production')` the names diverged and PM2 couldn't find the file. Upload now writes to `shared/<envFile>`; a `shared/.env` alias is also maintained so external scripts and the workDir-relative `. ./.env` keep working.

src/config/loader.ts

@@ -39,7 +39,11 @@ async function detectEnvFile(configFile: string, cwd: string): Promise<string> {
 }
 
 export async function loadConfig(cwd: string, configPath?: string): Promise<ShipnodeConfig> {
-  const file = configPath ?? resolve(cwd, 'shipnode.config.ts');
+  // Resolve against the user's cwd so `--config ./shipnode.frontend.config.ts`
+  // works the same as `--config shipnode.frontend.config.ts`. Without this,
+  // jiti's anchor is shipnode's own dist/ dir and relative paths blow up with
+  // "Cannot find module". `resolve()` returns absolute paths unchanged.
+  const file = configPath ? resolve(cwd, configPath) : resolve(cwd, 'shipnode.config.ts');
   await loadEnvIntoProcess(await detectEnvFile(file, cwd));
 
   const exists = await pathExists(file);

tests/unit/loader.test.ts

@@ -0,0 +1,47 @@
+import { describe, it, expect, beforeAll, afterAll } from 'vitest';
+import { mkdtemp, writeFile, rm } from 'node:fs/promises';
+import { tmpdir } from 'node:os';
+import { join } from 'node:path';
+import { loadConfig } from '../../src/config/loader.js';
+
+const minimalConfig = `
+import { shipnode } from '${join(process.cwd(), 'src/config/builder.ts').replace(/\\/g, '/')}';
+
+export default shipnode
+  .backend()
+  .ssh({ host: '1.2.3.4', user: 'deploy' })
+  .deployTo('/var/www/app')
+  .pm2('myapp')
+  .build();
+`;
+
+describe('loadConfig — --config path resolution', () => {
+  let dir: string;
+
+  beforeAll(async () => {
+    dir = await mkdtemp(join(tmpdir(), 'shipnode-loader-'));
+    await writeFile(join(dir, 'shipnode.custom.config.ts'), minimalConfig);
+  });
+
+  afterAll(async () => {
+    await rm(dir, { recursive: true, force: true });
+  });
+
+  it('resolves a relative --config path against cwd, not against shipnode dist/', async () => {
+    // Previously this threw "Cannot find module './shipnode.custom.config.ts'"
+    // because jiti's anchor is the loader file inside dist/.
+    const config = await loadConfig(dir, './shipnode.custom.config.ts');
+    expect(config.app).toBe('backend');
+    expect(config.remotePath).toBe('/var/www/app');
+  });
+
+  it('accepts a bare filename as --config (no ./ prefix)', async () => {
+    const config = await loadConfig(dir, 'shipnode.custom.config.ts');
+    expect(config.pm2?.apps[0].name).toBe('myapp');
+  });
+
+  it('still accepts an absolute --config path', async () => {
+    const config = await loadConfig(dir, join(dir, 'shipnode.custom.config.ts'));
+    expect(config.ssh.host).toBe('1.2.3.4');
+  });
+});