@unotest/web 0.30.0 → 0.32.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,4 +1,5 @@
1
- import { L as LintDiagnostic } from '../linter-CM2CpIyW.js';
1
+ import { L as LegacyLayout } from '../legacy-layout-By62PkbP.js';
2
+ import { L as LintDiagnostic } from '../linter-Yf4gPe5J.js';
2
3
  import '@unotest/dsl';
3
4
 
4
5
  /** Derive a viewer-compatible scenario name from an absolute scenario
@@ -24,19 +25,24 @@ declare function scenarioNotFoundMessage(arg: string, scenarioPath: string, cwd:
24
25
  * scenarios. Returns null for files in a subfolder or outside `unotest/e2e/`.
25
26
  * Exported only for tests. */
26
27
  declare function scenarioInRootDiagnostic(file: string, cwd: string): LintDiagnostic | null;
28
+ /** Report a project still on the pre-0.28 layout (`lint:legacy-layout`).
29
+ * A warning, not the loader's refusal: `lint` needs the config only for
30
+ * rule severity and the helpers dir, so it ran on the defaults — and says
31
+ * so, because a suite nobody can lint until it is migrated is a suite
32
+ * nobody lints during the migration. Anchored at the config nobody reads.
33
+ * Exported only for tests. */
34
+ declare function legacyLayoutDiagnostic(layout: LegacyLayout): {
35
+ file: string;
36
+ diagnostic: LintDiagnostic;
37
+ };
27
38
  /** Pull a global `--env <name>` / `--env=<name>` flag out of argv and set
28
39
  * `UNOTEST_ENV`, so the `.env.<name>` / `.secrets.<name>` overlays activate
29
40
  * for whichever subcommand runs (e2e / lint / viewer). Order-insensitive;
30
41
  * returns argv with the flag removed. An explicit shell `UNOTEST_ENV` is left
31
42
  * untouched when `--env` is absent. */
32
43
  declare function applyEnvFlag(args: string[]): string[];
33
- /** Argv as the subcommand sees it.
34
- *
35
- * `bundle` owns its own `--env`: it names an environment ON A BOX, not a
36
- * local `.env.<name>` overlay. Consuming it globally left `bundle push
37
- * --run --env prod` refusing to run with "--run needs --env" — the command
38
- * the box manual and every CI job use. */
44
+ /** Argv as the subcommand sees it. */
39
45
  declare function commandArgs(rawArgs: string[]): string[];
40
46
  declare function main(argv: string[]): void;
41
47
 
42
- export { applyEnvFlag, commandArgs, extraPositionalsError, main, scenarioInRootDiagnostic, scenarioNameFromPath, scenarioNotFoundMessage };
48
+ export { applyEnvFlag, commandArgs, extraPositionalsError, legacyLayoutDiagnostic, main, scenarioInRootDiagnostic, scenarioNameFromPath, scenarioNotFoundMessage };