Docs/frontend #128
Docs/frontend #128
Conversation
frontend/README.md
Outdated
|
|
||
| You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome! | ||
| After that, head to `near.org/flag` and enter the URL you got from the first step. If you have not changed any configurations then the default should be `http://127.0.0.1:3030` |
There was a problem hiding this comment.
nit: Would be nice to have a comment below explaining what that does specifically. Something like:
This changes the gateway to consume the widget from the URL provided instead of from on-chain.
There was a problem hiding this comment.
Agree, a more in-depth explanation would be really helpful here. Maybe you could have a section which explains; how widgets are sourced at a high-level and that bos-loader is needed to bypass the above
frontend/README.md
Outdated
|
|
||
| To learn more about Next.js, take a look at the following resources: | ||
| ```bash | ||
| bos-loader dev-queryapi.dataplatform.near --path widgets/src |
There was a problem hiding this comment.
This could be an npm script?
| bos-loader dev-queryapi.dataplatform.near --path widgets/src | |
| yarn serve-widgets |
frontend/README.md
Outdated
|
|
||
| You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome! | ||
| After that, head to `near.org/flag` and enter the URL you got from the first step. If you have not changed any configurations then the default should be `http://127.0.0.1:3030` |
There was a problem hiding this comment.
| After that, head to `near.org/flag` and enter the URL you got from the first step. If you have not changed any configurations then the default should be `http://127.0.0.1:3030` | |
| After that, head to `near.org/flags` and enter the URL you got from the first step. If you have not changed any configurations then the default should be `http://127.0.0.1:3030` |
frontend/README.md
Outdated
|
|
||
| You can check out [the Next.js GitHub repository](https://github.com/vercel/next.js/) - your feedback and contributions are welcome! | ||
| After that, head to `near.org/flag` and enter the URL you got from the first step. If you have not changed any configurations then the default should be `http://127.0.0.1:3030` |
There was a problem hiding this comment.
Agree, a more in-depth explanation would be really helpful here. Maybe you could have a section which explains; how widgets are sourced at a high-level and that bos-loader is needed to bypass the above
No description provided.