Skip to content

chore: shared TS config#10870

Open
jacob-ebey wants to merge 2 commits intomainfrom
shared_ts_config
Open

chore: shared TS config#10870
jacob-ebey wants to merge 2 commits intomainfrom
shared_ts_config

Conversation

@jacob-ebey
Copy link
Copy Markdown
Member

No description provided.

Copy link
Copy Markdown
Member

@mjackson mjackson left a comment

Choose a reason for hiding this comment

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

I'm not opposed to consolidating our tsconfigs. I'd just like to own it for a little while longer instead of introducing deps on @tsconfig/* packages for now.

Comment thread config/package.json
@@ -0,0 +1,8 @@
{
"private": true,
"name": "@remix-run/config",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's call this package @remix-run/tsconfig and keep it in the packages dir (even tho it's private) like everything else.

Comment thread config/tsconfig.json
@@ -0,0 +1,6 @@
{
"extends": ["@tsconfig/node22/tsconfig.json", "@tsconfig/node-ts/tsconfig.json"],
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Unless you feel strongly about this, I don't see a ton of value in extending these configs. They are small, and we have gotten this far without them. Let's just copy out the pieces we need and own this piece ourselves. I think we already had most of them in our own tsconfigs.

Comment thread pnpm-workspace.yaml
typescript: ^5.9.3

packages:
- config
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Let's keep this new package in packages/tsconfig instead of a new root directory.

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.

2 participants