mirror of
https://github.com/Comfy-Org/ComfyUI_frontend.git
synced 2026-01-26 19:09:52 +00:00
961af8731e
## Summary Split tailwind utils out to a shared package within the monorepo. ## Changes - Creates `@comfyorg/tailwind-utils` package - Does not require export, publishing, etc - Uses `export` to ensure this change does not impact other PRs (many imports to update) - If we _want_ to update all imports, there are two commits ready to be re-applied - e.g. `git revert 80960c2a82c0d1ac06eee1bb83ac333216b2b376` ## Review Focus - Is this pattern desirable? - Should we just include this in a broader design-system split? I kind of vote yes, but also it's a good small, first step. ┆Issue is synchronized with this [Notion page](https://www.notion.so/PR-5777-Split-Tailwind-utility-functions-out-to-a-shared-package-2796d73d3650815f976fc73b4fb86ef3) by [Unito](https://www.unito.io)
30 lines
573 B
JSON
30 lines
573 B
JSON
{
|
|
"name": "@comfyorg/tailwind-utils",
|
|
"version": "1.0.0",
|
|
"type": "module",
|
|
"description": "Shared Tailwind CSS utilities for ComfyUI Frontend",
|
|
"main": "./src/index.ts",
|
|
"types": "./src/index.ts",
|
|
"exports": {
|
|
".": {
|
|
"import": "./src/index.ts",
|
|
"types": "./src/index.ts"
|
|
}
|
|
},
|
|
"scripts": {
|
|
"typecheck": "tsc --noEmit"
|
|
},
|
|
"nx": {
|
|
"tags": [
|
|
"scope:shared",
|
|
"type:util"
|
|
]
|
|
},
|
|
"dependencies": {
|
|
"clsx": "^2.1.1",
|
|
"tailwind-merge": "^2.2.0"
|
|
},
|
|
"devDependencies": {
|
|
"typescript": "^5.4.5"
|
|
}
|
|
} |