Ok I understand this is confusing, but it should be harmless, you can ignore these errors. I’m guessing you’re defining some custom commands in your CONFIG page?
Some background on what’s happening here: to support certain new configuration options (specifically around indexing and sync) I now have to load your CONFIG file when the client boots, way before the whole editor is ready. The way I do this is by running the Lua code in the CONFIG page with some very limited set of APIs exposed (mostly only the config.* ones). Everything else is not yet available and will therefore fail “quietly” (the “but ignoring” is the quiet part). Later on, the full config is loaded properly and these errors shouldn’t reappear.
What of course is confusing here is that you still see those errors, so perhaps I’ll just hide them completely or mark them even more explicilty “THIS FAILED BUT IT’S OK!!!11” 
I’ll think if I’ll just mute errors entirely for a future release.
If you don’t like these errors, or perhaps even as a better practice: what you can do is simply move anything that’s not config.* calls from your CONFIG page to a separate page, e.g. Library/Commands, or call it whatever you like the name doesn’t matter. That should solve the issue (and may be cleaner anyway).