`'BLOG_ROOT' not set in .env file` shouldn't be in loop when build site

[Xavi Lee]

When I run yarn dev, I will get

...
$ NODE_OPTIONS='--no-warnings=ExperimentalWarning --loader ts-node/esm' node ./tool/cli.ts spas
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
'BLOG_ROOT' not set in .env file
Built 146 SPA related files
$ NODE_OPTIONS='--no-warnings=ExperimentalWarning --loader ts-node/esm' node ./tool/cli.ts gather-git-history
Wrote 9 _githistory.json files
$ NODE_OPTIONS='--no-warnings=ExperimentalWarning --loader ts-node/esm' node ./tool/cli.ts build-robots-txt
info: Generated client\build\robots.txt based on ALWAYS_ALLOW_ROBOTS=false
[OKAY] Loaded ENV .env File as KEY=VALUE Format
...

'BLOG_ROOT' not set in .env file should only appear once, multiple occurrences will give the impression that something wrong.