* upgrade tauri-plugin-shellx
* feat(shell): add killPid method to shell API with new permission
* fix: extension new window
* feat(shell): enhance process management and logging in extensions
- Add debug logging for extension process events
- Implement process tracking in UI worker
- Update shell API to support custom process recording
- Modify extension template to demonstrate process spawning
- Refactor shell command handling with improved error handling
* Add killPid extension API to @kksh/api
* chore(deps): update tauri-plugin-shellx-api to version 2.0.15
* pnpm lock
* chore(deps): update dependencies and lock file
- Upgrade ESLint to version 9.21.0
- Update @types/bun to version 1.2.3
- Bump various development dependencies
- Reorganize package.json dependencies in ui package
* chore(deps): update SvelteKit template dependencies
- Add @eslint/js version 9.21.0
- Update package.json dependency order
- Sync pnpm-lock.yaml with package.json changes
* chore: add eslint to desktop
* chore(deps): remove local tauri-plugin-shellx and use published version 2.0.15
* bump desktop to 0.1.28
* fix: change escape key behavior to navigate home instead of back
* feat: load custom ui extension with http server on Linux
Linux now uses the same loading approach as Windows due to a bug https://github.com/tauri-apps/tauri/issues/12767
* feat: add tauri-plugin-system-info-api dependency to deno.lock
* fix: update email field in KunkunExtManifest to be optional and nullable
* refactor: update Supabase type generation command and enhance database types structure
- Changed the Supabase type generation command to include a specific project reference and output path.
- Refactored the database types in `database.types.ts` for improved readability and added new fields, including `extension_state` and `package_json` in the `ext_publish` table.
- Ensured consistent formatting across type definitions for better maintainability.
* feat: add optional README path to ExtPackageJson and enhance tests for README retrieval
* feat: add optional readmeContent to ExtensionPublishValidationData and retrieve README in validateJsrPackageAsKunkunExtension
* feat: add optional readme field to database types for improved package metadata
* feat: enhance StoreExtDetail to display package metadata including author and contributors
- Added packageJson prop to StoreExtDetail for improved extension metadata display.
- Implemented rendering of author and contributors from packageJson.
- Integrated README content display in StoreExtDetail if available.
- Updated +page.svelte to parse and provide packageJson data using valibot for validation.
* feat: enhance TauriLink component to support conditional rendering based on Tauri environment
- Added detection for Tauri environment using the browser variable.
- Updated the TauriLink component to render a button when in Tauri, and an anchor tag for external links otherwise.
- Improved user experience by ensuring appropriate link behavior based on the application context.
* feat: add unpacked size to npm registry
* feat: replace size in ext_publish table to tarball_size, add unpacked_size (only applicable to npm)
* feat: add pretty-bytes dependency and update debug package version
- Added `pretty-bytes` package with version 6.1.1 to `package.json`.
- Updated `debug` package to use `supports-color@9.4.0` in `pnpm-lock.yaml` for improved compatibility.
* feat: add tarball_size field to database types for improved package metadata
* feat: add readme fetching for npm registry, readme from github
* fix: remove console.log from NPM API test to clean up output
* style: update extension store details
* style: update README section in StoreExtDetail component for improved styling
* fix: update command input placeholder text in English, Russian, and Chinese translations for clarity
* chore: bump version to 0.1.18 in package.json
* fix: lint
* chore: upgrade many dependencies
* fix: @kksh/svelte, migrate 5
* refactor: move dialog plugin code out of ui package
* chore: disable check-types in api build.ts
Causing build error in kunkun-services
* feat: add jsr package
* feat: implement jsr package with API and parsers for jsr
* feat: modify API, add function to extract linked github repo from html
* perf: improve jsr package API with @hk/jsr-client
* feat: add jsr package version table for publishing extension
* fix: dependency and type incompatibility in ui package
* feat: add validateJsrPackageAsKunkunExtension function in jsr package
* feat: improve jsr table
* feat: add a ElementAlert component
* feat: update ElementAlert UI
* chore: update deno.lock
* chore: enable submodule support in jsr-publish workflow
* chore: bump version to 0.0.48 in jsr.json
* feat: regenerate supabase types, add author_id
* Move @kksh/jsr package to @kksh/api
* update deno.lock
* chore: change @tauri-plugin/plugin-upload version from git url to version
* feat: add rounded corner for ElementAlert
* chore: update deno.lock
* chore: bump version to 0.0.51 in jsr.json and update import paths for ExtPackageJson
* feat: add publishExtJSR API to SupabaseAPI
* refactor: replace "@hk/jsr-client" from jsr with @huakunshen/jsr-client from npm
* chore: update deno.lock
* feat: update validateJsrPackageAsKunkunExtension return type
* refactor: improve error message
* feat: add metadata to ext_publish, update database.types.ts
* feat: add models module for Supabase with ExtPublishMetadata and source type enumeration
* feat: support installing JSR package as extension
Since JSR overwrites package.json with its own code to be compatible with npm, causing manifest parsing to be impossible. I add metadata field to ext_publish.
When extension comes from jsr, kunkun app will fetch the original package.json from jsr and overwrite the one modified by jsr.
* fix: add missing dep @tauri-apps/plugin-upload to @kksh/extension
* chore: update version to 0.0.52 in version.ts
* refactor: replace comlink with kkrpc
* fix: import path in api pkg and btn styling in ui iframe page
* fix: fixed fetch API from kkRPC migrate
* refactor: replace comlink-stdio with kkrpc
* update deno lock
* bump @kksh/api
* update API version
* publish api pkg again to fix kkrpc version
* update pnpm lock
* dep: fix dependency problems
* dep: update deno.lock
* chore: remove 2 submodules
they were added only for integration development
* update pnpm lock
* fix: test template path
* format: with prettier
* downgrade next version
* ci: try to fix next build on windows
* try to fix CI
* Revert "try to fix CI"
This reverts commit b9c63c392f50f1d2d3ceec406e49b1af2348c740.
* upgrade tauri-api-adapter
* try to fix next
* remove templates from pnpm workspace
* update CI test
* publish @kksh/api with upgraded tauri-api-adapter to fix nextjs template