Skip to content

Upgrade Biome and TypeScript dependencies with config adjustments#381

Open
jonaspm wants to merge 25 commits intobknd-io:release/0.21from
jonaspm:chore/upgrade-biome-ts
Open

Upgrade Biome and TypeScript dependencies with config adjustments#381
jonaspm wants to merge 25 commits intobknd-io:release/0.21from
jonaspm:chore/upgrade-biome-ts

Conversation

@jonaspm
Copy link
Copy Markdown
Contributor

@jonaspm jonaspm commented Mar 29, 2026

This pull request updates TypeScript and configuration files across the project to improve compatibility, maintainability, and developer experience. The main changes include upgrading all TypeScript dependencies to version 6.0.2, updating schema references for configuration files, and removing unnecessary baseUrl settings from various tsconfig.json files.

Dependency Upgrades:

  • Upgraded all typescript dependencies to version 6.0.2 in package.json files for the main app, documentation, and all example projects. [1] [2] [3] [4] [5] [6] [7] [8]

Configuration Improvements:

  • Added the $schema property to all tsconfig.json files to enable better IDE support and validation. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
  • Updated the $schema reference in biome.json to the latest version for improved tooling support.

Build and Path Settings Cleanup:

  • Removed the baseUrl property from tsconfig.json files in the main app, documentation, and several example projects to simplify TypeScript path resolution and avoid potential conflicts. [1] [2] [3] [4]

These changes ensure the project is up-to-date with the latest TypeScript features and best practices, while also streamlining configuration for easier maintenance.

@jonaspm
Copy link
Copy Markdown
Contributor Author

jonaspm commented Apr 2, 2026

@cameronapak is there anything else needed from my side to get this PR approved? 😄

@cameronapak cameronapak added the Seems Ready to Merge This PR appears to be ready to merge into the next release label Apr 3, 2026
@cameronapak
Copy link
Copy Markdown
Collaborator

cameronapak commented Apr 3, 2026

I personally walked through the code and it looks good to me.

My buddy DeepWiki said the following comments. If any of them are valid, please make updates. And then let me know when it's ready for re-review!

1. Inline comment on examples/cloudflare-vite-code/package.json (line with the typescript version):

Nit: This is an exact pin ("6.0.2") while the sibling examples/cloudflare-vite-hybrid/package.json uses "^6.0.2". Should this have a ^ prefix to match the rest of the project?


2. Inline comment on examples/nuxt/tsconfig.json (line 2, the $schema line):

Minor: This replaced the // https://nuxt.com/docs/guide/concepts/typescript comment. Since tsconfig supports JSONC, both could coexist — the Nuxt docs link is useful context for developers working with this example.


3. Inline comment on examples/waku/tsconfig.json (line 1):

This file was touched to remove downlevelIteration (good cleanup since target: "esnext" makes it a no-op), but it looks like the $schema addition that every other tsconfig got was missed here.


4. Top-level PR comment (review summary):

Nice work — this is clean and thorough! A few small things:

  • packages/postgres/package.json and packages/sqlocal/package.json still have "typescript": "^5.8.2". These are workspace packages and should probably be bumped to ^6.0.2 for consistency with the rest of the monorepo.
  • examples/cloudflare-vite-code/package.json uses an exact pin "6.0.2" while its sibling cloudflare-vite-hybrid uses "^6.0.2" — looks like a small oversight.
  • examples/waku/tsconfig.json is missing the $schema that was added to every other tsconfig.
  • examples/nuxt/tsconfig.json lost the helpful // https://nuxt.com/docs/guide/concepts/typescript comment — could be preserved alongside the new $schema.

Everything else looks good. The baseUrl removals are safe (verified the path resolution semantics), the Biome bump is clean, and the downlevelIteration removal in waku is correct.

Copy link
Copy Markdown
Collaborator

@cameronapak cameronapak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR looks good, @jonaspm! Approving.

Before we merge it in, please read and review #381 (comment) to see if anything small adjustments are necessary

@jonaspm
Copy link
Copy Markdown
Contributor Author

jonaspm commented Apr 3, 2026

This PR looks good, @jonaspm! Approving.

Before we merge it in, please read and review #381 (comment) to see if anything small adjustments are necessary

done 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Seems Ready to Merge This PR appears to be ready to merge into the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants