Fix running example on the web browser.

[blueorbitz]

No description provided.

[3Nigma]

Thank you very much for your work and interest, @blueorbitz . We are caught up a bit with other more burning, work-related, stuff but we'll look at your PR as soon as possible. 🙇

[3Nigma]

Didn't know the Provider class changed so drastically in later versions of the @hashgraph/sdk. Thank you for your work in pointing this out, @blueorbitz . We'll have to look into the options more thoroughly. Currently, Strato targets @hashgraph/sdk v2.11.3, I think.

I'll try to take a closer look at your changes during the weekend.

[3Nigma]

@blueorbitz , why are you saying that the repo is not working. If you clone it fresh and do

$ npm install
$ npm run build
$ npm start

you should be able to start serving the demo-app. You must go through the https url to be able to interact with the browser wallet extension.

[blueorbitz]

Anyway, as you suggested I tried doing the same to install a fresh build. This is what I was getting

I notice that the Provider is just an empty class, thus I think removing it should be just fine.

This is the second error I notice. It compiled just fine. Manage to prompt the approval from the Hashpack. Then this happens.

After fixing the super with super(opts.account.id, opts.account, null); it works for me. I am not too sure about your setup.

Foremostly, I tried to reduce the global dependency on the dev environment. I need to manually install @babel/core and @hashgraph/sdk to run the build. I think in this case, our library version may vary.

Another option you could opt for is to update the package.json with the proper version of the dependency. I think very likely this was the root cause for the errors.