mirror of https://github.com/pezkuwichain/pezkuwi-apps.git synced 2026-04-22 01:57:57 +00:00

Files

T

pezkuwichain 7a4bbeac25 fix: update extension packages and fix type compatibility for pezkuwi-sdk

- Update @pezkuwi/extension-inject to ^0.62.13 with proper /types exports
- Update @pezkuwi/extension-dapp to ^0.62.13
- Update @pezkuwi/extension-compat-metamask to ^0.62.13
- Fix IconTheme type to include 'bizinikiwi' and 'pezkuwi' themes
- Fix endpoint array issues (getTeleports -> direct array references)
- Add type assertions for external package compatibility (acala, moonbeam, parallel)
- Fix subspace.ts dynamic class typing
- Fix conviction type in page-referenda
- Update Pallet type names to Pezpallet prefix across codebase
- Define InjectedExtension types locally for module resolution
- Add styled-components DefaultTheme augmentation
- Add react-copy-to-clipboard type declaration for React 18

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

2026-01-08 16:24:19 +03:00

src

fix: update extension packages and fix type compatibility for pezkuwi-sdk

2026-01-08 16:24:19 +03:00

package.json

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

README.md

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

tsconfig.build.json

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

tsconfig.spec.json

feat: initial Pezkuwi Apps rebrand from polkadot-apps

2026-01-07 13:05:27 +03:00

README.md

@pezkuwi/apps-config

General config for various services, including settings, external links & types. This is a central source of all the configuration settings that can be tweaked. This also means that it can be customized (via PR) to support any additional chains. The internals are split into a number of settings -

api - Here you can add any chain or node-type specific types configuration. When added, it means that when the UI connects to either a runtime with a spec name, or a chain with a specific name, the types will be automatically added to the API as used in the app.
endpoints - Configuration for specific per-type chain endpoints.

Customization for each of these are discussed next.

Api

The API config can be done in one of two ways -

chain - Here we are mapping to a specific chain name. Generally the next type would be preferred, however if you are supporting multiple chains with individual configs, you would probably want to add the chain-specific information in here.
spec - Here we are mapping from the runtime spec name of the chain to specific types. This means that when connected to a specific spec, these types will be injected.

The actual type definitions you should be familiar with, it is exactly the same as you would upload via the settings page in JSON, or as detailed in the API types pages.

Endpoints

Add your chain logo (if available) to either ui/logos/chains or ui/logos/nodes (the second is generally used)
Run the image build command to generate an inline version via yarn build:images
Add your chain to endpoints/{production, productionRelay, testing, testingRelay*} as applicable for your deployment
The ui.color specifies the chain color, the ui.logo (imported from generated), specifies the specific logo