you don't know what he wants you to answer, just as he doesn't know why you designed it this way. In general, the interview mainly depends on your thinking, not how you have to do it or what you use.

give me a chestnut

first of all, I will say that the technologies I use are react family bucket webpack and es6

why react? Why webpack? Why es6?.
why not angular? Why not vue? Why not browserify? Why not es5?.

what he wants to hear is the whole idea and process of your project.
I see why there is no project requirements analysis mentioned above. Shouldn't we first analyze the business of the project, what needs to be done, and what are the requirements? And then choose the architecture?

well, there are different answers at different stages.

in terms of such a powerful word as architecture , maybe he wants to ask more than just your technical points.

for example:

• what is the workflow of the entire project?
• what is the process of collaboration between different people?
• what is the definition and interface of the interface?
• what testing method is used to enhance the robustness of the system?
• document establishment and improvement at all stages?

and so on.

of course, there is a very empty and general word or discipline, which is Software Engineering .
after all, software development is a systematic group brick-moving activity!

finally, as far as the front-end technology is concerned, the establishment of scaffolding, platform component library, front-end application, local performance optimization, etc.
as mentioned above, even if the existing mature open source solutions have their advantages and disadvantages, how to define and choose?
in case the business encounters the problem that the existing open source solution is not easy to deal with, how to think about and solve it.

in the end, there are no standard answers to these things, it depends on how you brag! I won't do it anyway, ha.

feels that the front-end small project has no structure at all, just use the official scaffolding to do it directly.
but if you pull hard, there are still a few points:
1.css.csss: in the configuration of public css, the css of each component is actually very small, and most of the css that can be reused can be extracted, such as utils;
2 in bootstrap. Permission control: backstage management websites all have this function
global configuration of 3.ajax requests: libraries such as axios can configure global requests and handle errors
4. Design and extraction of functional components and common modules
5. Responsive layout handling: if pc is compatible with mobile, you can also talk about page layout processing
6. Caching and updating
7. Data flow design
8.seo processing / unit testing, etc.
if it is your own packaging tool, you can also talk about the packaging design
in short, the interview is to talk about what you know, even if the question is wrong, it is better than not answering it. Experienced interviewers will dig deep into the things you have come into contact with to test you