-
Notifications
You must be signed in to change notification settings - Fork 4
update to aepp-sdk v12.0.0 #2
Comments
Thanks for the update @marc0olo, I will see to the update. |
Hello again @marc0olo, I have gone through the "Migration to 10.0.0" guide and I figured for on this boilerplate, nothing needs to be changed aside from updating the used package version. I will make the update now and await your feedback should in case I am missing something before making the commit. Thanks. |
Hi @emmanuelJet, yes, normally you should only have to update the package version :-) |
mhh. let's hope it's nothing serious. I will ask somebody of the team to have a look into the problem, too. thanks! here the action with the failed build: |
@emmanuelJet we can confirm there is an issue. I saw a workaround mentioned in a linked issue: maybe it works when adapting to it. but anyway - it's kind of sad it doesn't work out of the box with create-react-app. |
No need to do a workaround (actually proposals from the above issue didn't work for me), this is a configuration issue on sdk side |
Hello @davidyuk, Happy new week. Any update on the merge? I look forward to your response. Thanks, |
Hi @emmanuelJet! Currently, it is blocked by:
|
Hi @emmanuelJet, today we released v11.0.0 of the SDK. Can you please check again and update the boilerplate accordingly? Thanks! =) |
Hey @emmanuelJet, can you revisit this topic again with the recently released SDK v12.0.0? Would be awesome to have a react boilerplate that is up to date :) |
also, be aware of breaking changes! https://aeternity.com/aepp-sdk-js/v12.0.0/guides/migration/12.0.0/ |
today we released v10.0.0 of the sdk. would be good to have the boilerplate updated, too =)
The text was updated successfully, but these errors were encountered: