Duska.T d6839e36d6 test/ENG-6171/e2e failed tests investigation for v0.48.0 (#854)
* test: add aria labels to token components and temporarily disable token subtitle locator

* test(e2e): fix token management tests and improve accessibility and temp commented out

* Fix: Update currency balance container accessibility labels

* clean-up comments in swapVisuals.spec.ts

* clean up the commented code managementToken.spec.ts

* fix: added proper locators due to missing data-test-ids
2025-01-11 16:25:46 +01:00
2024-09-17 23:47:45 +01:00
2022-09-20 10:13:20 +02:00
2023-10-11 17:20:57 +08:00
2024-07-17 09:23:17 +01:00
2025-01-10 13:24:28 +00:00
2025-01-10 13:24:28 +00:00
2024-07-17 09:23:17 +01:00

xverse-extension

Installing and Running

Procedures

  1. Check if your Node.js version is >= 18.
  2. Clone this repository.
  3. Make sure you're logged in to the @secretkeylabs scope on the GitHub NPM package registry. See the Guide
    1. Create a GitHub personal access token (classic)
    2. Run npm login --scope=@secretkeylabs --registry=https://npm.pkg.github.com
    3. Username: GITHUB USERNAME Password: PERSONAL_ACCESS_TOKEN Email: PUBLIC-EMAIL-ADDRESS
  4. Add .env file (example: .env.example)
  5. Run npm install to install the dependencies.
  6. Run npm start
  7. Load your extension on Chrome following:
    1. Access chrome://extensions/
    2. Check Developer mode
    3. Click on Load unpacked extension
    4. Select the build folder.

Developing with local dependencies

Use esm build, and reference your filesystem in package.json

For example, if your xverse-core and xverse-web-extension are in same directory, make or pull your local changes to xverse-core, then:

cd ../xverse-core && npm i && npm run build:esm && \
cd $OLDPWD && npm i --legacy-peer-deps @secretkeylabs/xverse-core@../xverse-core && npm start
Description
No description provided
Readme 34 MiB
Languages
TypeScript 99%
JavaScript 0.5%
Shell 0.4%
CSS 0.1%