hunk.code_window:       });
         const { result } = await harness.executeOnce();
         expect(result?.success).toBe(true);
         harness.expectFile('dist/index.html').content.not.toContain(`<style`);
       });
  
hunk.labels: keep keep keep keep keep replace keep keep
hunk.after_edit:       harness
           .expectFile('dist/index.html')
           .content.toContain(
             `<link rel="stylesheet" href="styles.css" media="print" onload="this.media='all'">`,
           );
         harness.expectFile('dist/index.html').content.toContain(`body{color:#000;}`);
  
hunk.file_path: packages/angular_devkit/build_angular/src/builders/browser/tests/options/inline-critical_spec.ts
hunk.type: replace
file: A workspace has a single CLI configuration file, `angular.json`, at the top level.
  The `projects` object contains a configuration object for each project in the workspace.
  
  You can edit the configuration directly in a code editor,
  or indirectly on the command line using this command.
  
  The configurable property names match command option names,
  except that in the configuration file, all names must use camelCase,
  while on the command line options can be given in either camelCase or dash-case.
  
  For further details, see [Workspace Configuration](guide/workspace-config).
  
  For configuration of CLI usage analytics, see [Gathering an Viewing CLI Usage Analytics](./usage-analytics-gathering).
  