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
{{ message }}
This repository has been archived by the owner on May 13, 2022. It is now read-only.
With the new typescript library the microraiden.js must be compiled manually. We may want to check for its existence when starting the proxy and notify the user if it is missing.
The warning may be displayed both in the webui and in the proxy log.
The text was updated successfully, but these errors were encountered:
IMO, a warning in uppercase in the logs should be enough, instead of refusing to start, as it can be generated and will be available directly, no restart required. Also, it can be proxyed by e.g. nginx, so it may be available to the client but not in the usual folder. Don't think it should be done in the webui, as the webui doesn't start properly if there's no microraiden.js.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
With the new typescript library the
microraiden.js
must be compiled manually. We may want to check for its existence when starting the proxy and notify the user if it is missing.The warning may be displayed both in the webui and in the proxy log.
The text was updated successfully, but these errors were encountered: