From e087688da837c4493c2d3193c83fb2b87d71a1bf Mon Sep 17 00:00:00 2001 From: Josh Ford Date: Tue, 2 Jul 2024 06:29:06 -0700 Subject: [PATCH] minor grammar fix (#2104) --- blog/2024-07-01.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/blog/2024-07-01.md b/blog/2024-07-01.md index 30d5be99851..dfc2ae55f10 100644 --- a/blog/2024-07-01.md +++ b/blog/2024-07-01.md @@ -26,7 +26,7 @@ In order to act on this feedback and accomplish these goals, improvements had to During the alpha testing phase of this project, we anticipated a fairly straightforward path in resolving wider npm support but unfortunately, the team discovered a more complex scenario. While standard JavaScript packages work well, React UI libraries frequently encounter difficulties. These challenges stem from the unique packaging methods of each library and the complexities involved in synchronizing changes between the iframe and the outer DOM. Although we have identified several theoretical solutions, each requires further research and development to assess their practicality and effectiveness. This has been more fully detailed in [a GitHub discussion within the BWE Repo](https://github.com/near/react-on-chain/discussions/425). -We reached out to leading B.O.S. component contributors to determine whether this limitation would be unnegotiable and to learn what features they value most. Do they prioritize unrestricted NPM support over secure iframe composability? How important is composability, and how would they define it, considering our approach dissects it down to the atomic level of every element? +We reached out to leading B.O.S. component contributors to determine whether this limitation would be unnegotiable and to learn what features they value most. Do they prioritize unrestricted NPM support over secure iframe composability? How important is composability, and how would they define it? (considering our approach dissects it down to the atomic level of every element) This revealed some interesting findings, one of which was that secure composability on an atomic level was not at the top of the list. Most favored the ease of quick prototyping, deployment, and onboarding with managed infra and wallet connections. Many valued social-db features and the ability to create custom gateways (websites) using code and user data publicly available to them.