Alternatively this could also be a creep feature to transfer something from one storage to another without putting it in it's own cargo for a tick.
The max amount of transfered material could still be the current free cargo of the creep for balancing reasons
why don't you upgrade it a bit before it expires? I have done that in the past with sending one upgrader.
but I think that was when one upgrade resetted the whole timer I think .. don't know if it is still feasible.
have you updated screeps-mongo to the latest version? I'm currently running screeps server v4.0.3 with screeps-mongo without seeing this error.
I have some fixes in my branch (https://github.com/bastianh/typed-screeps/tree/ptr) ..
I think we discussed about using gitconsensus for the repo a few days ago?
I think it would be pretty easy to identify areas in rooms that would for example qualify to be displayed as a sea instead of a stone isle.
@tigga it could be a wall tile from the terrain type and a different api could reveal the type of the "wall"... besides stone and water maybe more visually different types would be possible.
If you don't like it named "TERRAIN_MASK_WALL" they could name it different and keep an alias with the WALL name.
maybe they use the already existing TERRAIN_MASK_LAVA in the future.
well .... since technically it would not differ from walls it could probably implemented as s cosmetic change without any changes to the api...
Looking forward to test it on my private server 
I could not find it, but I know this was discussed before.
I don't like the idea for various reasons. I think the cpu you can use should have a cap... and I think it would not be good for the market.
If considered it should have a high cost, but not in energy or credits but in cpu. ( So if you sell 500 cpu it would cost the seller 1000. )
if you want code only run exactly once you could save a flag in Memory for example.
could you please push it to npm ?