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
Currently it's possible to make mistake during development and our tools do not notice it because it generates the code which actually doesn't cause this issue (potentially older version of ES).
This is what happened during implementation of storage stats chart, everything worked locally in dev env but once it was deployed, /network-capacity endpoint failed with 500 error and then it was fixed -> #683
What
Either get rid of webpack and use ts-node + tsc or ensure that webpack generates the same code for both prod and development envs
The text was updated successfully, but these errors were encountered:
Why
Currently it's possible to make mistake during development and our tools do not notice it because it generates the code which actually doesn't cause this issue (potentially older version of ES).
This is what happened during implementation of storage stats chart, everything worked locally in dev env but once it was deployed,
/network-capacity
endpoint failed with 500 error and then it was fixed -> #683What
Either get rid of webpack and use
ts-node
+tsc
or ensure that webpack generates the same code for both prod and development envsThe text was updated successfully, but these errors were encountered: