improve gro gitops path handling and add a banner to the generated repos.ts

Author: ryanatkn

.changeset/heavy-countries-enjoy.md

@@ -0,0 +1,5 @@
+---
+'@ryanatkn/fuz_gitops': patch
+---
+
+improve `gro gitops` path handling and add a banner to the generated `repos.ts`

src/lib/gitops.task.ts

@@ -2,7 +2,7 @@ import type {Task} from '@ryanatkn/gro';
 import {z} from 'zod';
 import {readFile, writeFile} from 'node:fs/promises';
 import {format_file} from '@ryanatkn/gro/format_file.js';
-import {join} from 'node:path';
+import {basename, resolve} from 'node:path';
 import {paths, print_path} from '@ryanatkn/gro/paths.js';
 import {load_from_env} from '@ryanatkn/gro/env.js';
 import {load_fuz_config} from '@ryanatkn/fuz/config.js';
@@ -46,7 +46,7 @@ export const task: Task<Args> = {
 	run: async ({args, log, sveltekit_config}) => {
 		const {path, dir, outdir = sveltekit_config.routes_path} = args;
 
-		const outfile = join(outdir, 'repos.ts');
+		const outfile = resolve(outdir, 'repos.ts');
 
 		const fuz_config = await load_fuz_config(path, dir, log);
 
@@ -73,8 +73,14 @@ export const task: Task<Args> = {
 				: '@ryanatkn/fuz_gitops/fetch_deployments.js';
 
 		// JSON is faster to parse than JS so we optimize it by embedding the data as a string.
+		// TODO the `basename` is used here because we don't have an `origin_id` like with gen,
+		// and this file gets re-exported,
+		// and we don't want the file to change based on where it's being generated,
+		// because for example linking to a local package would change the contents
 		const contents = `
+			// generated by ${basename(import.meta.filename)}
 			import type {Deployment} from '${specifier}';
+
 			export const deployments: Deployment[] = ${embed_json(fetched_deployments)}
 		`;
 		// TODO think about possibly using the `gen` functionality in this task, not sure what the API design could look like