You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to sign a transaction directly on postman. It seems it should be possible to dynamically load a library as shown below but it is not working
Steps to Reproduce
In postman create a dummy request with the following Pre-request script
pm.sendRequest("https://unpkg.com/@bsv/sdk", (err, res) => {
//convert the response to text and save it as an environment variable
pm.collectionVariables.set("bsv", res.text());
// eval will evaluate the JavaScript code and initialize the min.js
eval(pm.collectionVariables.get("bsv"));
//use the library to sign a transaction and broadcast it via ARC
})
Send
Expected Behavior
Library is loaded and you can use it to sign, broadcast via ARC, etc.
Actual Behavior
Reference error: exports is not defined
Stack Traces or Screenshots
Environment
OS: Windows
Node version: n/a
@bsv/sdk version: 1.0.18
Additional Information
Not sure if this is actually a bug as this is a very specific use case
The text was updated successfully, but these errors were encountered:
Bug Description
I wanted to sign a transaction directly on postman. It seems it should be possible to dynamically load a library as shown below but it is not working
Steps to Reproduce
In postman create a dummy request with the following Pre-request script
pm.sendRequest("https://unpkg.com/@bsv/sdk", (err, res) => {
//convert the response to text and save it as an environment variable
pm.collectionVariables.set("bsv", res.text());
// eval will evaluate the JavaScript code and initialize the min.js
eval(pm.collectionVariables.get("bsv"));
//use the library to sign a transaction and broadcast it via ARC
})
Expected Behavior
Library is loaded and you can use it to sign, broadcast via ARC, etc.
Actual Behavior
Reference error: exports is not defined
Stack Traces or Screenshots
Environment
@bsv/sdk
version: 1.0.18Additional Information
Not sure if this is actually a bug as this is a very specific use case
The text was updated successfully, but these errors were encountered: