renovate
a32174d5d8
This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [eslint-plugin-simple-import-sort](https://github.com/lydell/eslint-plugin-simple-import-sort) | [`12.1.1` → `13.0.0`](https://renovatebot.com/diffs/npm/eslint-plugin-simple-import-sort/12.1.1/13.0.0) |  |  | --- ### Release Notes <details> <summary>lydell/eslint-plugin-simple-import-sort (eslint-plugin-simple-import-sort)</summary> ### [`v13.0.0`](https://github.com/lydell/eslint-plugin-simple-import-sort/blob/HEAD/CHANGELOG.md#Version-1300-2026-04-06) [Compare Source](https://github.com/lydell/eslint-plugin-simple-import-sort/compare/v12.1.1...v13.0.0) This release puts imports from the same source, but with different import styles, in a deterministic order. ```js // First namespace imports: import * as Circle from "circle; // Then default imports: import createCircle from "circle"; // Then named imports: import { radius } from "circle"; ``` That is especially useful if you need to have both a namespace import *and* want to import a few things separately (since that cannot be combined into a single import statement). With the above rule, the imports end up in a deterministic order. It’s only a breaking change if you import from the same source multiple times in the same file (using different styles), and only in the form that you need to autofix your files. Thanks to Kannan Goundan ([@​cakoose](https://github.com/cakoose))! </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xMDQuMSIsInVwZGF0ZWRJblZlciI6IjQzLjEwNC4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Reviewed-on: #166 Co-authored-by: Renovate Bot <renovate@unbound.se> Co-committed-by: Renovate Bot <renovate@unbound.se>
Unbound Schemas - Web UI
A Nuxt 4 application with Vuetify for viewing and managing federated GraphQL schemas.
Features
- 📊 Dashboard with schema statistics and recent updates
- 📝 View all published schemas by ref (production, staging, etc.)
- 🔍 Search and filter schemas
- 📄 View schema SDL (Schema Definition Language)
- 📥 Download and copy schemas
- 🌳 View merged supergraphs for each ref
- 🎨 Modern Material Design UI with Vuetify
Environment Variables
Create a .env file in the root directory:
NUXT_PUBLIC_API_BASE=http://localhost:8080
The API base URL points to your GraphQL Schema Registry backend service.
Setup
Make sure to install dependencies:
# npm
npm install
# pnpm
pnpm install
# yarn
yarn install
# bun
bun install
Development Server
Start the development server on http://localhost:3500:
# npm
npm run dev
# pnpm
pnpm dev
# yarn
yarn dev
# bun
bun run dev
Production
Build the application for production:
# npm
npm run build
# pnpm
pnpm build
# yarn
yarn build
# bun
bun run build
Locally preview production build:
# npm
npm run preview
# pnpm
pnpm preview
# yarn
yarn preview
# bun
bun run preview
Check out the deployment documentation for more information.