server-mock | a simple mock server for ajax testing | Mock library

Vue CLI's serve command uses the mode option to load environment variables from mode-specific .env files. It also sets the NODE_ENV to one of the three standard modes (test, development, or production) only if not already set. However, if the specified mode is not standard (as is the case with mock), Vue CLI defaults to development.

So, you could set NODE_ENV=mock inside .env.mock to bypass the NODE_ENV setting mentioned above.

Alternatively, you could set NODE_ENV on the NPM script's command line in *nix shells:

The problems described above occurred as a result of bad dynamic importing. Somewhere else in my project I had two dynamic imports, where one of them was a parent of the other one. The "random" occurrance described above was the result of whether the first or the second import won the race (although why it resulted in the way it did is puzzling me).

This means I had to make sure import1 came before import2, which I simply solved with

Your timeout may be firing before you get your data. Instead of calling the setDayData from your ngOnInit, you probably want to call it from the body of your getDayInfo subscribe block.

This will make sure you have the data and your follow up methods are called after you receive the data.