\n \n setNamespace(e.target.value as NamespaceUrl)}\n />\n
\n
\n \n setName(e.target.value as NamespaceUrl)}\n />\n
\n
\n \n setSchema(e.target.value)}\n />\n
\n \n \n\n {createdSchema &&
{`Schema Name: ${createdSchema.name}`}
}\n
\n )\n}\n\nrender(, document.getElementById('root'))\n```\n\n## Troubleshoots\n\n1. `ERR_UNSUPPORTED_DIR_IMPORT` error on the nextjs project\n\n In case you encounter the `ERR_UNSUPPORTED_DIR_IMPORT` error while utilizing this SDK in your Next.js project, simply include the following configuration to the next.config.js file. For more details, please refer to _[here](https://nextjs.org/blog/next-11-1#es-modules-support)_\n\n```js\n//...\nexperimental: {\n esmExternals: false,\n},\n//...\n```\n\n## Migration guide from `@futureverse/asset-registry-react` package\n\nThe new package name for this library is now `@futureverse/asset-register-react`. Hence, there are some files\nand codes that have been renamed in the new version. Here are the migration guides:\n\n- The package dependency `@futureverse/asset-registry` has been changed to refer to `@futureverse/asset-register`\n- Renamed files:\n - `./src/hooks/AssetRegistryClientProvider.tsx` file is now `./src/hooks/AssetRegisterClientProvider.tsx`\n - `./src/hooks/useAssetRegistryClientContext.ts` file is now `./src/hooks/useAssetRegisterClientContext.ts`\n- `AssetRegistryClientProvider` provider class is now `AssetRegisterClientProvider`\n- `useAssetRegistryClientContext` React hook is now `useAssetRegisterClientContext`\n","readmeFilename":"README.md"}