From d0361662f30d5f1082b5bd591d6fe6ec68e28474 Mon Sep 17 00:00:00 2001 From: Oleksii Kosynskyi Date: Thu, 21 Sep 2023 21:31:29 -0400 Subject: [PATCH] 6366 Add instructions to the doc for the plugin naming (#6446) --- docs/docs/guides/web3_plugin_guide/plugin_authors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/guides/web3_plugin_guide/plugin_authors.md b/docs/docs/guides/web3_plugin_guide/plugin_authors.md index 0abe86e63c6..f7f057edd07 100644 --- a/docs/docs/guides/web3_plugin_guide/plugin_authors.md +++ b/docs/docs/guides/web3_plugin_guide/plugin_authors.md @@ -19,7 +19,7 @@ To provide type safety and IntelliSense for your plugin users, please refer to t At the minimum, your plugin should depend on `web3` package version `4.0.2`. This will allow your plugin class to extend the provided `Web3PluginBase` abstract class. However, `web3` shouldn't be listed as a regular dependency, instead it should be listed in your plugin's `package.json` as a [peer dependency](https://nodejs.org/en/blog/npm/peer-dependencies/). :::important -If the version `web3@4.0.2`, was not available yet. You can use the version `web3@4.0.2-dev.af57eae.0`. +It is important to note that the plugin name should be structured as `@/web3-plugin-` or `web3-plugin-`. ::: ```json