@dbx-tools/projen 0.5.0 → 0.5.1

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.
package/package.json CHANGED
@@ -32,7 +32,7 @@
32
32
  },
33
33
  "main": "index.ts",
34
34
  "license": "Apache-2.0",
35
- "version": "0.5.0",
35
+ "version": "0.5.1",
36
36
  "types": "index.ts",
37
37
  "type": "module",
38
38
  "exports": {
package/src/project.ts CHANGED
@@ -22,7 +22,7 @@ import { applyCompiledPublish } from "./publish.ts";
22
22
  import { DBXToolsRelease, type StandaloneRelease } from "./release.ts";
23
23
  import { AGNOSTIC_COMPILER_OPTIONS, PACKAGE_TAG_MIXINS, type PackageTag } from "./tags.ts";
24
24
  import { DBXToolsRootTsconfig } from "./tsconfig.ts";
25
- import { ViteConfigFile } from "./vite.ts";
25
+ import { DEFAULT_VITE_OVERRIDES, ViteConfigFile } from "./vite.ts";
26
26
  import { DBXToolsVsCode } from "./vscode.ts";
27
27
  import {
28
28
  DEFAULT_PACKAGE_ROOTS,
@@ -864,6 +864,12 @@ function initProject(
864
864
  eslint.addIgnorePattern(`${root}/**/index.ts`);
865
865
  }
866
866
  eslint.addIgnorePattern("**/vite.config.ts");
867
+ // The unmanaged vite overrides live at the package root, outside any `src/**`
868
+ // tsconfig include, so the type-aware parser cannot resolve them to a project.
869
+ // They are hand-authored (not generated), but ESLint still cannot parse them.
870
+ for (const override of DEFAULT_VITE_OVERRIDES) {
871
+ eslint.addIgnorePattern(`**/${override}`);
872
+ }
867
873
  // Codegen packages declare `codegen.inputs` via mixins after construction; ignore
868
874
  // their `src/` once manifests are known (preSynthesize), same reason as openapi.
869
875
  new EslintIgnoreCodegen(project);
package/src/vite.ts CHANGED
@@ -24,8 +24,12 @@ import { type Project, TextFile } from "projen";
24
24
  * (later wins, absent files skipped). Both extensions are accepted so an existing
25
25
  * JavaScript override keeps working; the TypeScript one is listed last so it wins
26
26
  * where a package is mid-migration and still has both.
27
+ *
28
+ * Exported because ESLint has to ignore them: an override is a package-ROOT file
29
+ * outside any `src/**` tsconfig include, so the type-aware parser cannot resolve
30
+ * it to a project - the same reason the generated `vite.config.ts` is ignored.
27
31
  */
28
- const DEFAULT_VITE_OVERRIDES = ["vite.config.override.js", "vite.config.override.ts"];
32
+ export const DEFAULT_VITE_OVERRIDES = ["vite.config.override.js", "vite.config.override.ts"];
29
33
 
30
34
  /** Render the generated `vite.config.ts` source with the override chain inlined. */
31
35
  function renderViteConfig(overridePaths: string[]): string {