nango/packages/data-ingestion · na/nango

GGitHubchore: make tsconfigs compatible with typescript-go (#6593)

文件	最后提交记录	最后更新时间
lib	chore: make tsconfigs compatible with typescript-go (#6593) ## Problem Step 3 of the ESLint → oxlint migration (NAN-5769). oxlint's type-aware mode runs on the native `typescript-go` compiler (via `oxlint-tsgolint`), which has dropped several legacy tsconfig options we still use. Until they're migrated, type-aware linting errors out on the affected packages, so those files wouldn't actually be type-checked. All of these are changes we'd need for newer TypeScript regardless. ## Solution Migrate each removed option to its modern equivalent: - root `tsconfig.json` — drop `ignoreDeprecations: "5.0"` + `importsNotUsedAsValues: "remove"`, add `verbatimModuleSyntax: true` - `packages/webapp` + `packages/connect-ui` — remove `baseUrl`; the `@/` alias still resolves via the relative `paths` entry (tsc) and the explicit Vite `alias` (build), both independent of `baseUrl` - `scripts/one-off/` (3 tsconfigs)** — `moduleResolution: "Node"` (node10, removed) → `"Bundler"` `verbatimModuleSyntax` surfaced one value/type export to split (`BigQueryType` in `data-ingestion`); the rest of the codebase was already compliant since `consistent-type-imports` enforces `import type`. Prereq NAN-5809 (posthog-node v5) is already on master, so `verbatimModuleSyntax` no longer trips the old posthog packaging bug. Part of NAN-5769. Sub-issue: NAN-5810. ## Testing - `npm run ts-build` passes clean (exit 0) with `verbatimModuleSyntax` enabled - `@/` alias resolution confirmed unaffected — webapp/connect-ui resolve it via an explicit Vite `alias`, not tsconfig `baseUrl` - (Follow-up) `oxlint --type-aware .` reports zero `tsconfig-error` diagnostics — verified during the migration spike	2 个月前
.gitignore	(feat) [nan-591] insert into bigQuery (#1903) ## Describe your changes Add in BigQuery data ingestion from sync, actions, and webhooks ## Issue ticket number and link NAN-591 ## Checklist before requesting a review (skip if just adding/editing APIs & templates) - [ ] I added tests, otherwise the reason is: - [ ] I added observability, otherwise the reason is: - [ ] I added analytics, otherwise the reason is:	2 年前
package.json	fix: upgrade dependencies (#4393) ## Changes Upgrade dependencies - Some related to recent different CVEs (axios, concurrently, babel, bigquery, soap) - Some because they are "mostly" consequence-free (vitest, vite, prettier, etc.) <!-- Summary by @propel-code-bot --> --- This PR performs a comprehensive upgrade of both production and development dependencies across nearly all packages in the monorepo, targeting security CVEs and routine version hygiene (notably for axios, concurrently, babel, bigquery, soap, vitest, vite, prettier, etc.). The only direct source code change is a refactor of the errorToObject function in packages/utils/lib/errors.ts, now handling primitives and null/undefined values more robustly with improved type safety. Test infrastructure is updated to consistently use vitest 3.2.4 across all sub-packages, while several minor test improvements are included. There are no application or business logic changes. <details> <summary><strong>Key Changes</strong></summary> • Upgraded critical dependencies to resolve CVEs: axios, concurrently, babel, bigquery, soap, and others. • Updated developer tooling (vitest, vite, prettier, tsx, etc.), standardizing on vitest 3.2.4. • Refined packages/utils/lib/errors.ts: errorToObject now explicitly handles primitives and null/undefined; type annotation updated. • Synchronized dependency versions across workspace package.json files. • Added or restored mocks cleanup in critical runner package tests (sdk.unit.test.ts), improving test reliability. </details> <details> <summary><strong>Affected Areas</strong></summary> • All package.json files across the monorepo • Dependency lock files (omitted for size) • packages/utils/lib/errors.ts (utilities error handling) • Test suites (notably runner, utils, and related packages) </details> This summary was automatically generated by @propel-code-bot	1 年前
tsconfig.json	(feat) [nan-591] insert into bigQuery (#1903) ## Describe your changes Add in BigQuery data ingestion from sync, actions, and webhooks ## Issue ticket number and link NAN-591 ## Checklist before requesting a review (skip if just adding/editing APIs & templates) - [ ] I added tests, otherwise the reason is: - [ ] I added observability, otherwise the reason is: - [ ] I added analytics, otherwise the reason is:	2 年前