transport.transport0X.raiden.network(where X is a number)
Hi @andrevmatos , I've started integrating the
raiden-ts library into my frontend, I installed version 0.15 from npm. But I'm having issues with the bundler. I have added both of these babel plugins ("@babel/plugin-proposal-nullish-coalescing-operator", "@babel/plugin-syntax-optional-chaining") and this preset ("@babel/preset-typescript"), but the error persists:
(I can't seem to paste nicely formatted code into gitter - I'd swear it was a chat made for non-programmers... )
raiden-cli). We used to have a legacy ES5 build as well, but decided to ditch it in order to push for the end-user projects to customize their build options and adapt to the latest and most efficient language syntaxes whenever possible. We'll be looking in your issue, but seems like your babel project isn't properly being able to recognize these newish syntax.
raiden-ts/tsconfig.cjs.jsonand rebuilding. With a single-line patch, the codebase can also be made compatible with ES5 target if needed, but I'd say it'd be worth it to get your project compatible with more modern dependencies, as you'll get goodies by transpiling whatever needed at the end, instead of using legacy libs builds which may end up bundled in a non-optimized manner.
create-react-app, and they have had ES2020 support for some time and is a very well maintained project. It is the first library npm library that I've ever come across that doesn't work with
react-scripts. Anyway, I'll try bundle it myself
service-registry register --help
Hi guys, please i am getting this error when i try to create a channel using axios with this payload, Any Idea what could be wrong?
raiden-dapp/.env*files for examples on how to do so with the dApp, and
--helpon raiden-cli/raiden-py for the full clients.
raidennetwork/raiden:develop. Is this version the correct one to use for ongoing development? Should I remove the locally cached version to get the latest develop version?
https://pfs.demo001.env.raiden.networkfor my pathfinding service address and
https://transport.demo001.env.raiden.networkfor my matrix server. I got theses addresses from the .env.production file in the light client. Are these addresses usable?
https://transport.demo001.env.raiden.networkas our matrix server address and this was causing the inconsistencies. However I changed it to
transport.transport01.raiden.networkand the issues were gone. Still not sure why one address would work and the other doesn't (if someone could explain I'd appreciate it) but for now I have no issues.