cms.js | Client-Side JavaScript Site Generator

According to some threads about that starter, there's a bug about the Sass loaders that causes this issue. You have many solutions provided in this GitHub thread:

• Add options to the gatsby-plugin-sass:

The issue seems to be related to the favicon path, ensure that the path is correct and try changing it to other dummy image.

If the paths are correct this issue is likely due to an outdated dev-dependency (@babel/helper-compilation-targets) or, according to this GitHub thread it could be also due to an invalid version of libvips dependency. In both cases you can try the same solution:

Remove your lock file (package-lock.json or yarn-lock.json), and your node_modules folder and reinstall your dependencies with yarn install or npm install. If the issue persists, try:

Your paths for media_folder and public_folder should be something like:

I've faced the same issue a few days ago and I felt just like you, there's a lack of information (or is not properly linked between) so finally, I've managed to achieve this.

If I understood correctly, do you want to add, moreover of some others identities, a typical username and password identity, isn't? I'll try to lead you through those options.

First of all, in your config.yml you need to set up the identity gateway:

Comments for this article are coming from this request: https://user.guancha.cn/comment/cmt-list.json?codeId=440605&codeType=1&pageNo=1&order=1&ff=www

Here you can see some important variables: codeId (which is some kind of articleid, this number is being set on article's page, you can see it in page's source) and cursor for paginating - pageNo.

So, you just need to get codeId for interested article and crawl all comments for it from this endpoint (cmt-list.json). Response is json, so it's easy to parse comment's data.