Skip to content

feat(config): add shared TypeScript config package - #7

Merged
edwintantawi merged 5 commits into
mainfrom
feat/config-typescript
Sep 12, 2026
Merged

edwintantawi merged 5 commits into
mainfrom
feat/config-typescript

Conversation

@edwintantawi

Copy link
Copy Markdown
Member

Adds @batik/config, the workspace's shared tooling configuration package, starting with TypeScript configs.

What's in it

Five TypeScript configs, exported via subpath exports so consumers extend @batik/config/typescript/tsconfig.<name>.json:

  • tsconfig.base.json — strict settings shared by everything
  • tsconfig.browser.json / tsconfig.node.json — environment layers
  • tsconfig.library.json / tsconfig.react.json — target layers

The package ships src directly (no build step) and declares typescript >=5.8 as a peer dependency.

Workspace root tsconfig

The root tsconfig.json is a real project rather than a files: [] solution stub: it owns the Node-side files that live outside any package's shipped source — the root vite.config.ts and each package's build config.

Those build configs stay here on purpose. A package's tsconfig is a browser program with types: [], so pulling vite.config.ts into it would drag Node type references into the same program and let process, Buffer and __dirname resolve inside src/, silently defeating the isolation.

No project references — tsdown builds the packages and tsgolint checks them.

Notes

Changeset included (minor for @batik/config).

Introduce @batik/config with base/browser/node/react/library tsconfig
presets, and wire the workspace root tsconfig to extend it.
@changeset-bot

changeset-bot Bot commented Sep 12, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: a97118e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@batik/config Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

The root tsconfig extends `@batik/config/typescript/tsconfig.node.json`,
a bare specifier resolved through node_modules. pnpm only symlinks a
workspace package that is declared as a dependency, so the extends target
did not exist and `vp check` failed with "Invalid tsconfig".

That config also sets `types: ["node"]`, which needs `@types/node` present
at the root. Add it to the catalog pinned to 24.x, matching the Node
version pinned in devEngines.
@edwintantawi edwintantawi self-assigned this Sep 12, 2026
@edwintantawi
edwintantawi merged commit a35e399 into main Sep 12, 2026
3 checks passed
@edwintantawi
edwintantawi deleted the feat/config-typescript branch September 12, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant