The PUBLIC_URL env var is meant to be set to the full public URL of the instance (eg https://example.com). When it's set to an absolute path (or the default) /, Directus will mostly work, but can fail in some unexpected ways (eg emails will send with the wrong links, some public assets can't be loaded, etc.

We should show a warning in terminal on startup when PUBLIC_URL is an invalid URL

https://leapgraph.com/graphql-api-security

This article mentions several add-on packages that Reaction may want to use. This issue is simply to investigate whether these vulnerabilities are present and try adding the packages to solve them.

Currently, catch block is the same for both methods in useForgotPasswordFactory (https://github.com/vuestorefront/vue-storefront/pull/5971/files/0e001721be751b0b0130915023ea0867722e1065#diff-89077440c1264480ee6ffbbcfb08d6c64c9881bea61ebbd8e0e5d260085b66ad):

err.message = err?.graphQLErrors?.[0]?.message || err.message;

Let's create an external function that takes care of that a

when browsing, i should be able to perf-check right from the browser and results should be siphoned back to the extension.

各位好，

• 非常开心大家对于crawlergo的认可，但目前由于本人工作原因，可能无法及时的去挨个实现大家的需求，我会利用空余时间去实现比较有价值的特性和一些比较严重的BUG，更新速度可能是以月为单位，还请各位见谅。
• 有一些常见问题之前的issue已经提到并解决，大家在提新的issue时，请先看看closed
  的issue，说不定能找到解决办法。

@9ian1i