[skip ci] contribution guide and readme update

.vscode/tasks.json

@@ -319,7 +319,7 @@
               "poa_core",
               "eth_goerli",
               "eth",
-              "local",
+              "localhost",
             ],
             "default": ""
         },

CODE_OF_CONDUCT.md

+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at andrew@poa.network. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
\ No newline at end of file

README.md

-<h1 align="center">Blockscout frontend app</h1>
+<h1 align="center">Blockscout frontend</h1>
 
 <p align="center">
     <span>Frontend application for </span>
     <a href="https://github.com/blockscout/blockscout/blob/master/README.md">Blockscout</a>
     <span> blockchain explorer</span>
 </p>
+[![](https://dcbadge.vercel.app/api/server/blockscout?style=flat)](https://discord.gg/blockscout)
+docker pull blockscout/blockscout:latest
 
+## Running and configuring the app
 
-## App running and configuration
+App is distributed as a docker image. Here you can find information about the [package](https://github.com/blockscout/frontend/pkgs/container/frontend) and its recent [releases](https://github.com/blockscout/frontend/releases).
 
-App is distributed as a docker image. Info about the package and its recent releases you can find [here](https://github.com/blockscout/frontend/pkgs/container/frontend).
+You can configure your app by passing necessary environment variables when stating the container. See full list of ENVs and their description [here](./docs/ENVS.md).
 
-You can configure your app by passing necessary environment variables when stating a container. See full list of envs and their description [here](./docs/ENVS.md).
+```sh
+docker run -p 3000:3000 --env-file <path-to-your-env-file> ghcr.io/blockscout/frontend:latest
+```
 
-## Development
+Alternatively, you can build your own docker image and run your app from that. Please follow this [guide](./docs/CUSTOM_BUILD.md).
 
-### Technology stack
+## Contributing
 
-Core technologies what used in the project are
-- [yarn](https://yarnpkg.com/) as package manager
-- [React](https://reactjs.org/) as UI library
-- [Next.js](https://nextjs.org/) as application framework
-- [Chakra](https://chakra-ui.com/) as component library; our theme customization could be found in `/theme` folder
-- [jest]() as JavaScript testing framework
-- [playwright](https://playwright.dev/) as a tool for components visual testing
+See our [Contribution guide](./docs/CONTRIBUTING.md) for pull request protocol. We expect contributors to follow our [code of conduct](./CODE_OF_CONDUCT.md) when submitting code or comments.
 
-And of course our premier language is [Typescript](https://www.typescriptlang.org/)
+## Resources
+- [App ENVs list](./docs/ENVS.md)
+- [Contribution guide](./docs/CONTRIBUTING.md)
+- [Making custom build](./docs/CUSTOM_BUILD.md)
 
------
-### Local Development
+## License
 
-**Pre-requisites** You should have installed Node.js v16. The best way to manage your local Node.js version is [nvm](https://github.com/nvm-sh/nvm)
+[![License: GPL v3.0](https://img.shields.io/badge/License-GPL%20v3-blue.svg)](https://www.gnu.org/licenses/gpl-3.0)
 
-For local development please follow next steps:
-- clone repo
-- install dependencies with `yarn`
-- clone `.env.example` into `configs/envs/.env.secrets` and fill it with necessary secret values (see description [below](#environment-variables))
-- to spin up local dev server
-    - for predefined networks configs (see full available list in `package.json`) you can just run `yarn dev:<app_name>`
-    - for custom network setup create `.env.local` file with all required environment variables from the [list](#environment-variables) and run `yarn dev`
-- navigate to the host from logs output
-
-### Components visual testing
-
-We use [playwright experimental components testing](https://playwright.dev/docs/test-components) for visual (screenshots) CI check. Test renders a single component in headless browser in docker, generates screenshots and then compares this screenshot with a reference one.
-To perform testing locally you need to install docker and run `yarn test:pw:docker`
-
-### Building and running your own docker image
-
-For building a docker image simply run `yarn build:docker` or alternatively run `docker build` and pass your own args.
-
-For running app container from freshly built image with your local env config at `./.end.local` use `yarn start:docker:local` command or run `docker run` manually.
-
-*Disclaimer* Do no try to generate production build of the app on your local machine (outside the docker), it will fail.
+This project is licensed under the GNU General Public License v3.0. See the [LICENSE](LICENSE) file for details.
\ No newline at end of file

configs/envs/.env.eth

+# Set of ENVs for Ethereum network explorer
+# https://eth.blockscout.com/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.eth_goerli

+# Set of ENVs for Goerli testnet network explorer
+# https://eth-goerli.blockscout.com/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.jest

+# Set of ENVs for Jest unit tests
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.localhost

+# Set of ENVs for local network explorer
+# frontend app URL - https://localhost:3000/
+# API URL - https://localhost:3001/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost
-NEXT_PUBLIC_APP_PORT=3333
+NEXT_PUBLIC_APP_PORT=3000
 NEXT_PUBLIC_APP_INSTANCE=local
 NEXT_PUBLIC_APP_ENV=development
 
@@ -26,7 +30,7 @@ NEXT_PUBLIC_MARKETPLACE_SUBMIT_FORM=https://airtable.com/shrqUAcjgGJ4jU88C
 NEXT_PUBLIC_NETWORK_RPC_URL=https://core.poa.network
 
 # api config
-NEXT_PUBLIC_API_BASE_PATH=/poa/core
+NEXT_PUBLIC_API_BASE_PATH=/
 NEXT_PUBLIC_API_HOST=localhost
 NEXT_PUBLIC_API_PROTOCOL=http
 NEXT_PUBLIC_API_PORT=3001
\ No newline at end of file

configs/envs/.env.main

+# Set of ENVs for Develompent network explorer
+# https://blockscout-main.k8s-dev.blockscout.com/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.main.L2

+# Set of ENVs for Develompent L2 network explorer
+# https://blockscout-optimism-goerli.k8s-dev.blockscout.com/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.poa_core

+# Set of ENVs for POA network explorer
+# https://blockscout.com/poa/core/
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

configs/envs/.env.pw

+# Set of ENVs for Playwright components tests
+
 # app config
 NEXT_PUBLIC_APP_PROTOCOL=http
 NEXT_PUBLIC_APP_HOST=localhost

docs/CONTRIBUTING.md

+# Contribution guide
+
+Thanks for showing interest to contribute to Blockscout. The following steps will get you up and running.
+
+## Project setup
+
+1. Fork the repo by clicking <kbd>Fork</kbd> button at the top of the repo main page and name it appropriately
+
+2. Clone your fork locally
+    ```sh
+    git clone https://github.com/<your_github_username>/<fork_name>.git
+    cd <fork_name>
+    ```
+
+3. Make sure you're running Node.js 18+ and NPM 8+; if not, upgrade it accordingly, for example using [nvm](https://github.com/nvm-sh/nvm).
+    ```sh
+    node -v
+    npm -v
+    ```
+
+4. Install dependencies
+    ```sh
+    yarn
+    ```
+
+## Toolkit
+
+We are using following technology stack in the project
+- [Yarn](https://yarnpkg.com/) as package manager
+- [ReactJS](https://reactjs.org/) as UI library
+- [Next.js](https://nextjs.org/) as application framework
+- [Chakra](https://chakra-ui.com/) as component library; our theme customization could be found in `/theme` folder
+- [TanStack Query](https://tanstack.com/query/v4/docs/react/overview/) for fetching, caching and updating data from the API
+- [Jest](https://jestjs.io/) as JavaScript testing framework
+- [Playwright](https://playwright.dev/) as a tool for components visual testing
+
+And of course our premier language is [Typescript](https://www.typescriptlang.org/).
+
+## Local development
+
+1. Prepare your environment variables:  
+    - clone `.env.example` into `configs/envs/.env.secrets` and fill it with necessary secrets for the [external services](./ENVS.md#external-services-configuration) integration; you can pick up only those that your needed
+    - choose one of the following options:  
+        A. create `.env.local` file in the root folder with environment variables from the [list](./ENVS.md); all required variables should be present in the file;  
+        B. pick up one of the predefined configurations located at `/configs/envs` folder; no actual action is needed at this stage;
+2. Run your local dev server:
+    - if you picked up option "A" above, use `yarn dev` command
+    - if your options is "B", use `yarn dev:<config_name>` command
+3. In browser navigate to the URL from the command output (by default, it is `http://localhost:3000`)
+
+## Adding new dependencies
+For all types of dependencies:
+- **Do not add** a dependency if the desired functionality is easily implementable
+- If adding a dependency is necessary, please be sure that is is well-maintained and trustworthy
+
+## Adding new ENV variable
+
+*Note*, if the variable should be exposed to the browser don't forget to add prefix `NEXT_PUBLIC_` to its name.
+
+These are the steps that you have to follow to make everything work:
+1. Register variable placeholder in file `.env.template`; this is the most important step, without this the app will not receive variable value at run-time
+2. Document variable in the [/docs/ENVS.md](./ENVS.md) file; provide short description, its expected type, requirement flag, default and example value
+3. Make sure that you have added a property to React app config (`/configs/app/config.ts`) that is associated with this variable; do not use ENV variable values directly in the application code
+4. For local development purposes add the variable with its appropriate values to pre-defined ENV configs `/configs/envs` where it is needed
+5. Add the variable to CI configs where it is needed
+    - `deploy/values/review/values.yaml.gotmpl` - review development environment
+    - `deploy/values/main/values.yaml` - main development environment
+    - `deploy/values/review-l2/values.yaml.gotmpl` - review development environment for L2 networks
+    - `deploy/values/l2-optimism-goerli/values.yaml` - main development environment
+6. Don't forget to mention in the PR notes that new ENV variable were added  
+
+## Writing & Running Tests
+
+Every feature or bugfix should be accompanied by tests, either unit tests or component visual tests, or both, except from trivial fixes (for example, typo fix). All commands for running tests you can find [below](./CONTRIBUTING.md#command-list).
+
+### Jest unit tests
+
+If your changes only related to the logic of the app and not to its visual presentation, then try to write unit tests using [Jest](https://jestjs.io/) framework and [React Testing Library](https://testing-library.com/docs/react-testing-library/intro/). In general these tests are "cheaper" and faster than Playwright ones. Use them for testing your utilities and React hooks, as well as the whole components logic. 
+
+Place your test suites in `.test.ts` or `.test.tsx` files. You can find or add some mocks or other helpful utilities for these tests purposes in the `/jest` folder. 
+
+*Note*, that we are using custom renderer and wrapper in all test for React components, so please do not import package `@testing-library/react` directly in your test suites, instead use imports from `jest/lib` utility.
+
+### Playwright components tests
+
+For changes associated with the UI itself write components visual tests using [Playwright](https://playwright.dev/) framework and its *experimental* [Components test library](https://playwright.dev/docs/test-components). Please be aware of known [issues and limitations](https://playwright.dev/docs/test-components#known-issues-and-limitations) of this library.
+
+Your tests files should have `.pw.tsx` extension. All configs, mocks, fixtures and other utilities for these tests live in `/playwright` folder.
+
+We have 3 pre-configured projects. You can run your test with the desired project by simply adding its [tag](https://playwright.dev/docs/test-annotations#tag-tests) to the test name:
+- `default` - default project for all test, uses desktop Chrome desktop device; don't need to specify its tag, instead use `-@default` tag to skip test run with this project
+- `mobile` - project for testing on mobile devices, uses Safari mobile browser; add tag `+@mobile` to run test with this project
+- `dark-color-mode` - project for testing app in the dark color mode, uses desktop Chrome desktop device with forced dark color mode; add tag `+@dark-mode` to run test with this project.
+
+*Note* that, since we are developing not on the same operating system as our CI system, we have to use Docker to generate or update the screenshots. In order to do that use `yarn test:pw:docker <path-to-file> --update-snapshots` command. Please **do not commit** any screenshots generated via `yarn test:pw:local` command, their associated tests will fail in the CI run.
+
+## Making a Pull Request
+
+### Steps to PR
+
+1. Make sure that you fork and clone repo; check if the main branch has all recent changes from the original repo
+
+    > Tip: Keep your `main` branch pointing at the original repository and make pull
+    > requests from branches on your fork. To do this, run:
+    >
+    > ```
+    > git remote add upstream https://github.com/blockscout/frontend.git
+    > git fetch upstream
+    > git branch --set-upstream-to=upstream/main main
+    > ```
+    >
+    > This will add the original repository as a "remote" called "upstream," Then
+    > fetch the git information from that remote, then set your local `main` branch
+    > to use the upstream main branch whenever you run `git pull`. Then you can make
+    > all of your pull request branches based on this `main` branch. Whenever you
+    > want to update your version of `main`, do a regular `git pull`.
+
+2. Create a branch for your PR with `git checkout -b <your-branch-name>`; we do not follow any branch name convention just yet
+3. Commit your changes. Commits should be one logical change that still allows all tests to pass. Prefer smaller commits if there could be two levels of logic grouping. The goal is to allow contributors in the future (including your future self) to determine your reasoning for making changes and to allow them to cherry-pick, patch or port those changes in isolation to other branches or forks. Again, there is no strict commit message convention, but make sure that it clear and fully describes all changes that were made
+4. If during your PR you reveal a pre-existing bug, try to isolate the bug and fix it on an independent branch and PR it first
+5. Where possible, please provide unit tests that demonstrate new functionality or bug fix is working
+
+### Opening PR and getting it accepted
+
+1. Push your changes and create a Pull Request. If you are still working on the task, please use "Draft Pull Request" option, so we know that it is not ready yet. In addition, you can add label "WIP" to your PR, so all CI checks will not be triggered. 
+2. Once you finish your work, remove label "WIP" from PR, if it was added before, and publish PR if it was in the draft state
+3. Make sure that all code checks and tests are successfully passed
+4. Add description to your Pull Request and link an existing issue(s) that it is fixing
+5. Request review from one or all core team members: @tom2drum, @isstuev. Our core team are committed to reviewing patches in a timely manner.
+6. After code review is done, we merge pull requests by squashing all commits and editing the commit message if necessary using the GitHub user interface.
+
+*Note*, if you Pull Request contains any changes that are not backwards compatible with the previous versions of the app, please specify them in PR description and add label ["breaking changes"](https://github.com/blockscout/frontend/labels/breaking%20changes) to it.
+
+## Command list
+
+| Command | Description |
+| --- | --- |
+| **Running and building** |
+| `yarn dev` | run local dev server with user's configuration |
+| `yarn dev:<config_name>` | run local dev server with predefined configuration |
+| `yarn build:docker` | build a docker image locally |
+| `yarn start:docker:local` | start an application from previously built local docker image with user's configuration |
+| `yarn start:docker:poa_core` | start an application from previously built local docker image with predefined configuration for POA network explorer |
+| **Linting and formatting** |
+| `yarn lint:eslint` | lint project files with ESLint |
+| `yarn lint:eslint:fix` | lint project files with ESLint and automatically fix problems |
+| `yarn lint:tsc` | compile project typescript files using TypeScript Compiler |
+| `yarn format-svg` | format and optimize SVG icons in the `/icons` folder using SVGO tool |
+| **Testing** |
+| `yarn test:jest` | run all Jest unit tests |
+| `yarn test:jest:watch` | run all Jest unit tests in watch mode |
+| `yarn test:pw:local` | run Playwright component tests locally |
+| `yarn test:pw:docker` | run Playwright component tests in docker container |
+| `yarn test:pw:ci` | run Playwright component tests in CI |
+
+## Tips & Tricks
+
+### Code Editor
+
+#### VSCode
+
+There are some predefined tasks for all commands described above. You can see its full list by pressing <kbd>cmd + shift + P</kbd> and using command `Task: Run task`
+
+Also there is a Jest test launch configuration for debugging and running current test file in the watch mode.
\ No newline at end of file

docs/CUSTOM_BUILD.md

+# Building and running your own docker image
+
+You are free to clone the repo and make any changes to the application code that you want, adding your own customization and features. After that you can build a docker image by running `yarn build:docker` or alternatively run `docker build` and pass your own args that is necessary.
+
+For running app container from freshly built image do
+```sh
+docker run -p 3000:3000 --env-file <path-to-your-env-file> <your-image-tag>
+```
+
+*Disclaimer* Do no try to generate production build of the app on your local machine (outside the docker). The app will not work as you would expect.

docs/ENVS.md

@@ -2,7 +2,7 @@
 
 The app instance could be customized by passing following variables to NodeJS environment at runtime. See their list below.
 
-**IMPORTANT NOTE!** For _production_ build purposes all json-like values should be single-quoted. If it contains a hash (`#`) or a dollar-sign (`$`) the whole value should be wrapped in single quotes as well (see `dotenv` [readme](https://github.com/bkeepers/dotenv#variable-substitution))
+**IMPORTANT NOTE!** For _production_ build purposes all json-like values should be single-quoted. If it contains a hash (`#`) or a dollar-sign (`$`) the whole value should be wrapped in single quotes as well (see `dotenv` [readme](https://github.com/bkeepers/dotenv#variable-substitution) for the reference)
 
 ## Network configuration
 
@@ -164,20 +164,3 @@ For each application, you need to specify the `MarketplaceCategoryId` to which i
 | Variable | Type| Description | Is required  | Default value | Example value |
 | --- | --- | --- | --- | --- | --- |
 | NEXT_PUBLIC_HAS_BEACON_CHAIN | `boolean` | Set to true for networks with the beacon chain | - | - | `true` |
-
-
-
-
-# How to add new environment variable
-
-If the variable should be exposed to the browser don't forget to add prefix `NEXT_PUBLIC_` to its name.
-
-These are the steps that you have to follow to make everything work:
-- create the variable placeholder for build-time in file `.env.template`; this is the most important step, without this the app will not receive any variables that are passed at run-time
-- for local development purposes add the variable to either `configs/envs/.env.common` or `configs/envs/.env.<network>` files depending on if the variable has the same value for all network or specific value for each network
-- add the variable to CI configs
-    - `deploy/values/review/values.yaml` - review environment
-    - `deploy/values/main/values.yaml` - production environment
-    - `deploy/values/e2e/values.yaml` - e2e-test environment
-
-Keep in mind that all json-like values should be single-quoted, e.g `[{'foo': 'bar'}]`

package.json

 {
-  "name": "block-scout",
-  "version": "0.1.0",
-  "private": true,
+  "name": "blockscout-frontend",
+  "version": "1.0.0",
+  "private": false,
   "homepage": "https://github.com/blockscout/frontend#readme",
   "engines": {
     "node": "18",
@@ -9,17 +9,17 @@
   },
   "scripts": {
     "dev": "next dev",
-    "dev:local": "./node_modules/.bin/dotenv -e ./configs/envs/.env.localhost -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
+    "dev:localhost": "./node_modules/.bin/dotenv -e ./configs/envs/.env.localhost -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "dev:main": "./node_modules/.bin/dotenv -e ./configs/envs/.env.main -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "dev:main:L2": "./node_modules/.bin/dotenv -e ./configs/envs/.env.main.L2 -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "dev:poa_core": "./node_modules/.bin/dotenv -e ./configs/envs/.env.poa_core -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "dev:eth_goerli": "./node_modules/.bin/dotenv -e ./configs/envs/.env.eth_goerli -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "dev:eth": "./node_modules/.bin/dotenv -e ./configs/envs/.env.eth -e ./configs/envs/.env.secrets -- bash -c 'next dev -- -p \"$NEXT_PUBLIC_APP_PORT\"' | ./node_modules/.bin/pino-pretty",
     "build": "next build",
-    "build:docker": "docker build --build-arg GIT_COMMIT_SHA=$(git rev-parse HEAD) -t blockscout ./",
+    "build:docker": "docker build --build-arg GIT_COMMIT_SHA=$(git rev-parse HEAD) -t blockscout-frontend ./",
     "start": "next start",
-    "start:docker:local": "docker run -p 3000:3000 --env-file .env.local blockscout",
-    "start:docker:poa_core": "docker run -p 3000:3000 --env-file ./configs/envs/.env.poa_core --env-file ./configs/envs/.env.secrets blockscout",
+    "start:docker:local": "docker run -p 3000:3000 --env-file .env.local blockscout-frontend",
+    "start:docker:poa_core": "docker run -p 3000:3000 --env-file ./configs/envs/.env.poa_core --env-file ./configs/envs/.env.secrets blockscout-frontend",
     "lint:eslint": "./node_modules/.bin/eslint . --ext .js,.jsx,.ts,.tsx",
     "lint:eslint:fix": "./node_modules/.bin/eslint . --ext .js,.jsx,.ts,.tsx --fix",
     "lint:tsc": "./node_modules/.bin/tsc -p ./tsconfig.json",