mirror of
https://github.com/kunkunsh/kunkun.git
synced 2025-04-03 22:26:43 +00:00
48e2e47f96
* remove supabase package * upgrade valibot * removed supabase package Migration not complete yet * update submodule * fixed some supabase errors * Add new fields to extension models - Added `id` field to `ExtPublish` - Expanded `DBExtension` with multiple new properties: - `api_version`, `author_id`, `created_at`, - `downloads`, `icon`, `identifier`, - `long_description`, `name`, - `readme`, `short_description`, - and `tarball_size` * Refactor: clean up unused Supabase imports - Removed commented-out Supabase imports from various files to streamline the codebase. - Updated `created_at` type in `ExtPublish` model from `date` to `string` for consistency. * update icon enum to union * fix type errors after removing supabase * format * more types fixed * feat: enhance command handling and update SDK version
To extend the base.json config, use relative path
"extends": "@kksh/typescript-config/base.json" // no
"extends": "../typescript-config/base.json" // yes
Because the path alias is resolved relative to the file that extends the config.
If you install "@kksh/typescript-config": "workspace:*" in the package.json,
@kksh/typescript-config actually points to node_modules/packages/typescript-config,
and the path alias cannot be correctly resolved. (will need to add another ../).
"paths": {
"@kksh/ui/*": ["../../packages/ui/*"]
}
needs to become
"paths": {
"@kksh/ui/*": ["../../../packages/ui/*"]
}
to "escape" from node_modules.
So I'd rather use relative path to extend the config.