testnet support

README.md

@@ -579,6 +579,7 @@ const getAccountIdHandler = (request, response) => {
 }
 
 // NearSocialBridgeCore widget is the core that makes all the "magic" happens
+// use `wendersonpires.testnet/widget/NearSocialBridgeCore` as source if you want to use "testnet" environment
 return (
   <Widget
     src={'wendersonpires.near/widget/NearSocialBridgeCore'}
@@ -593,6 +594,8 @@ return (
 )
 ```
 
+**testnet:** Use `wendersonpires.testnet/widget/NearSocialBridgeCore` while creating your application using the testnet environment.
+
 And that's basically it. Again, remember that once your application is running inside the Widget, if it is making requests, you must handle each one of them inside the Widget, otherwise the unhandled requests will fail.
 
 ## Good to know

package.json

@@ -1,6 +1,6 @@
 {
   "name": "near-social-bridge",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "This library allows you to create a common application using ReactJS and inject it in a controlled way into a Widget on Near Social. Therefore, the Widget talks to the React application and vice versa, making it possible to consume Discovery API resources within the React application.",
   "main": "./dist/cjs/index.js",
   "module": "./index.js",

widget-setup.js

@@ -55,6 +55,7 @@ const getAccountIdHandler = (request, response) => {
   response(request).send({ accountId })
 }
 
+// use `wendersonpires.testnet/widget/NearSocialBridgeCore` as source if you want to use "testnet" environment
 return (
   <Widget
     src={'wendersonpires.near/widget/NearSocialBridgeCore'}