tequ
tequ
https://xrpl.org/docs/references/client-libraries/ https://xrpl.org/ja/docs/references/client-libraries/
https://github.com/XRPLF/xrpl-dev-portal/blob/f74f61149c8de2b32bdbf86ae8d190531159c3e2/docs/_snippets/common-links.md Especially in entries that are used in both Japanese and English, such as `[API v1]: /docs/references/http-websocket-apis/api-conventions/request-formatting.md#api-versioning`, it currently will only take you to the English page.
https://github.com/XRPLF/xrpl-dev-portal/blob/f74f61149c8de2b32bdbf86ae8d190531159c3e2/sidebars.yaml#L11 It makes no sense to manage custom titles for each page in translations.yaml.
on tablet size This image is iPad Air size
```ts import { useThemeHooks } from '@redocly/theme/core/hooks'; ... const { usePageSharedData } = useThemeHooks(); ``` Used in the following files - @theme/markdoc/components.tsx - blog/index.page.tsx - resources/code-samples.page.tsx
- ttREMIT - ttUNL_REPORT - ttEMIT_FAILURE - ttHOOK_SET (already exists) - ttCLAIM_REWARD - ttGENESIS_MINT - ttIMPORT - ttINVOKE - ttURITOKEN_MINT - ttURITOKEN_BURN - ttURITOKEN_BUY - ttURITOKEN_CREATE_SELL_OFFER - ttURITOKEN_CANCEL_SELL_OFFER
The package published or the dependency contains `process` code and will not work in the vite environment. https://vitejs.dev/guide/env-and-mode
to Readme file eg) ```md npm start -- -p 4001 ```
https://xrpl.org/docs/references/xrp-ledger-toml#validators > An HTTPS URL where one can find the list of other validators this validator trusts. If the validator is configured to use a validator list site for UNL...