Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
"cloudflare:preview": "turbo cloudflare:preview",
"deploy": "turbo deploy",
"dev": "turbo dev",
"format": "turbo prettier:fix lint:fix",
"format": "turbo //#prettier:fix prettier:fix lint:fix",
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"format": "turbo //#prettier:fix prettier:fix lint:fix",
"format": "turbo //#prettier:fix lint:fix",

Copy link
Member

Choose a reason for hiding this comment

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

Couldn't this also be node --run prettier:fix && turbo lint:fix, since we don't even need turbo for prettier?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Since rest of the commands were only using turbo-based approach so gave preference to that.

But yeah, we can definitely use direct node.js execution for prettier & turbo for linting. Also then if we don't need turbo for prettier, we should remove the prettier tasks from turbo.json?

"lint": "turbo lint",
"lint:fix": "turbo lint:fix",
"lint:staged": "lint-staged",
Expand Down
3 changes: 3 additions & 0 deletions turbo.json
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@
"//#prettier": {
"outputs": [".prettiercache"]
},
"//#prettier:fix": {
"outputs": [".prettiercache"]
},
"build": {
"dependsOn": ["^topo"]
},
Expand Down
Loading