Fix @generateTypes producing empty output when schema file has env-like name (#550)

* Initial plan

* Fix @generateTypes not including variables when using custom-named schema file as --path entry point

Agent-Logs-Url: https://github.com/dmno-dev/varlock/sessions/53e5a64d-4a9e-4f24-9054-1c8ce5e1b690

Co-authored-by: philmillman <3722211+philmillman@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: philmillman <3722211+philmillman@users.noreply.github.com>

Author: Copilot

.changeset/fix-typegen-custom-path-env-specific.md

@@ -0,0 +1,9 @@
+---
+"varlock": patch
+---
+
+Fix `@generateTypes` not creating variables when using a custom path with `varlock typegen --path <file>`
+
+When a schema file with an environment-qualifier-like name (e.g. `.env.infra.schema`) was passed as the explicit entry point via `--path`, its variables were being excluded from type generation. The filename was parsed such that `infra` was treated as an environment name (`applyForEnv='infra'`), causing the data source to be marked as environment-specific and all its variables to be filtered out.
+
+The fix ensures that a file loaded as the root entry point (no parent data source) is never treated as environment-specific, even if its filename contains an environment qualifier.

packages/varlock/src/env-graph/lib/data-source.ts

@@ -109,9 +109,11 @@ export abstract class EnvGraphDataSource {
    * Note: `applyForEnv` from filename parsing is only relevant for auto-loaded files.
    * Explicitly imported files (via `@import`) are controlled by the import mechanism,
    * not the auto-load-by-env logic, so their `applyForEnv` is ignored here.
+   * Similarly, a file that is the explicit root entry point (no parent) is never
+   * treated as env-specific even if its filename contains an env qualifier.
    */
   get isEnvSpecific(): boolean {
-    if (this.applyForEnv && !this.isImport) return true;
+    if (this.applyForEnv && !this.isImport && this.parent) return true;
     if (this.type === 'overrides') return true;
     if (this._hasConditionalDisable) return true;
     if (this.importMeta?.isConditionallyEnabled) return true;

packages/varlock/src/env-graph/test/type-generation.test.ts

@@ -196,6 +196,33 @@ describe('type generation', () => {
       expect(extrasSource).toBeDefined();
       expect(extrasSource!.isEnvSpecific).toBe(false);
     });
+
+    test('root entry file with env-like name (e.g. .env.infra.schema) is NOT isEnvSpecific', async () => {
+      // Regression test for: @generateTypes doesn't create variables when using
+      // a custom path with `varlock typegen --path .env.infra.schema`
+      // The filename `.env.infra.schema` was being parsed such that applyForEnv='infra',
+      // causing isEnvSpecific=true and all items being excluded from type generation.
+      const g = new EnvGraph();
+      await g.setRootDataSource(new DotEnvFileDataSource('.env.infra.schema', {
+        overrideContents: outdent`
+          # @defaultSensitive=false
+          # ---
+          TEST_A_B="1"
+          TEST_A_C="1"
+        `,
+      }));
+      await g.finishLoad();
+
+      // The root source should NOT be marked as env-specific
+      const rootSource = g.rootDataSource!;
+      expect(rootSource.isEnvSpecific).toBe(false);
+
+      // Items should be included in defsForTypeGeneration
+      expect(g.configSchema.TEST_A_B).toBeDefined();
+      expect(g.configSchema.TEST_A_B.defsForTypeGeneration.length).toBeGreaterThan(0);
+      expect(g.configSchema.TEST_A_C).toBeDefined();
+      expect(g.configSchema.TEST_A_C.defsForTypeGeneration.length).toBeGreaterThan(0);
+    });
   });
 
   describe('getTypeGenInfo - basic schema properties', () => {