Front-end engineering construction method, device, equipment, medium and product

Abstract

The embodiment of the invention provides a front-end engineering construction method and device, equipment, a medium and a product. The method comprises the following steps: receiving a construction request comprising an identifier of a target prototype version, and providing a first interface comprising component information according to a first configuration file; providing a second interface according to a first component selected by the user on the first interface, and determining a target component of a corresponding version according to a first version selected by the user on the second interface; and according to the first configuration file, putting the obtained scaffold and the target component under a construction directory for code integration so as to construct a front-end project. According to the scheme of the invention, the target prototype version representing the specific scaffold structure is determined according to the construction request, the first configuration file comprises the mountable component and the version of the component, and the user demand is received through the interactive interface, so that the automatic process of demand receiving and engineering construction is realized, the repeated configuration is reduced, and the construction efficiency is improved. Therefore, the front-end engineering development efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of front-end development technology, and in particular to a front-end engineering construction method, device, equipment, medium and product. Background Art

[0002] Front-end engineering refers to building interfaces and functions that users interact with directly in the browser through a series of technologies and tools. It not only involves code writing, but also includes performance optimization, automated construction, cross-platform compatibility, security assurance, and user experience design.

[0003] When constructing a front-end project, a general scaffold is first built. On the basis of the general scaffold, different usage scenarios are considered and different components are installed to achieve functional requirements. However, when continuing to develop on the general scaffold, the general scaffold needs to be reconfigured according to the installed components, resulting in repeated configuration and construction steps each time the front-end project is built, thereby reducing the development efficiency of the front-end project. Therefore, the current problem that needs to be solved is how to improve the efficiency of front-end project development. Summary of the invention

[0004] The embodiments of the present application provide a front-end engineering construction method, device, equipment, medium and product to improve the efficiency of front-end engineering development.

[0005] In a first aspect, an embodiment of the present application provides a front-end engineering construction method, comprising: receiving a construction request, the construction request including an identifier of a target prototype version; providing a first interface according to a first configuration file, the first interface including component information under the target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of a scaffold corresponding to each prototype version; different prototype versions correspond to different scaffold structures; providing a second interface according to a first component selected by a user on the first interface, and determining a target component of a corresponding version according to the first version selected by the user on the second interface; wherein the second interface includes a version range of the first component; obtaining a scaffold and a target component corresponding to the target prototype version according to the first configuration file; placing the scaffold and the target component corresponding to the target prototype version into a construction directory for code integration to construct a front-end engineering project.

[0006] In a possible implementation, the target component includes a basic target component; and the first interface includes basic component information under the target prototype version.

[0007] In one possible implementation, the target component also includes a dependent target component; the method also includes: if the currently determined target component is a basic component, providing a third interface, the third interface including component information of dependent components that depend on the target component; providing a fourth interface based on the second component selected by the user in the third interface, the fourth interface including the version range of the second component; based on the second version selected by the user in the fourth interface, determining the component of the corresponding version and adding it to the target component.

[0008] In one possible implementation, each scaffold and each version component is stored in a package management platform; according to the first configuration file, the scaffold and target component corresponding to the target prototype version are obtained, including: sending a download request to the package management platform, the download request including the coordinates of the scaffold and the coordinates of the target component corresponding to the target prototype version; receiving the scaffold and target component corresponding to the target prototype version returned by the package management platform.

[0009] In a possible implementation, the method further includes: maintaining a second configuration file, the second configuration file including project information of each front-end project, the project information including historical operations of prototype versions, scaffolds, and components under the front-end project.

[0010] In a possible implementation, the method also includes: receiving a requirement for adding a component, the requirement for adding a component is used to add a component under the first front-end project; determining the prototype version and the currently included version components of the first front-end project according to the second configuration file, and providing a fifth interface according to the first configuration file; the fifth interface includes component information under the prototype version of the first front-end project, except for the version components currently included in the first front-end project; providing a sixth interface according to the new component selected by the user in the fifth interface, and determining the target new component according to the third version selected by the user in the sixth interface; wherein the sixth interface includes the version range of the new component; obtaining the target new component according to the coordinates of the target new component in the first configuration file, and placing the target new component in the build directory of the first front-end project for code integration.

[0011] In a possible implementation, the method also includes: receiving a component update requirement, the component update requirement is used to update the component under the second front-end project; determining the prototype version and the currently included version components of the second front-end project according to the second configuration file, and providing a seventh interface according to the first configuration file; the seventh interface includes component information of the version components currently included in the second front-end project; providing an eighth interface according to the update component selected by the user in the seventh interface, and determining the target update component according to the fourth version selected by the user in the eighth interface; wherein the eighth interface includes the version range of the update component except the current version under the second front-end project; obtaining the target update component according to the coordinates of the target update component in the first configuration file, and overwriting the current version component under the build directory of the second front-end project with the target update component, and performing code integration.

[0012] In a possible implementation, after receiving the build request, it also includes: pushing the build template information of the target prototype version, the build template information includes the target component corresponding to the target prototype version in the historical build; and building the front-end project according to the build template selected by the user.

[0013] In a second aspect, an embodiment of the present application provides a front-end engineering construction device, comprising: a receiving module, used to receive a construction request, the construction request includes an identifier of a target prototype version; a providing module, used to provide a first interface according to a first configuration file, the first interface includes component information under the target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of a scaffold corresponding to each prototype version; different prototype versions correspond to different scaffold structures; an obtaining module, used to provide a second interface according to a first component selected by a user on the first interface, and determine a target component of a corresponding version according to the first version selected by the user on the second interface; wherein the second interface includes a version range of the first component; according to the first configuration file, the scaffold and target component corresponding to the target prototype version are obtained; a construction module, used to place the scaffold and target component corresponding to the target prototype version into a construction directory for code integration to construct a front-end engineering.

[0014] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a memory, a processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the processor executes the first aspect above and / or various possible implementations of the first aspect.

[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the first aspect above and / or various possible implementations of the first aspect.

[0016] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the above first aspect and / or various possible implementation methods of the first aspect.

[0017] The front-end engineering construction method, device, equipment, medium and product provided in the embodiment of the present application, by receiving a construction request including the identification of the target prototype version, provides a first interface including component information according to a first configuration file; provides a second interface according to the first component selected by the user in the first interface, and determines the target component of the corresponding version according to the first version selected by the user in the second interface; according to the first configuration file, the obtained scaffolding and target components are placed in the construction directory for code integration to build the front-end engineering. The scheme of the present application determines the target prototype version representing a specific scaffolding structure according to the construction request, the first configuration file includes the components that can be installed and the versions of the components, and receives user requirements through an interactive interface, realizes the automated process of demand reception and engineering construction and reduces repetitive configuration, thereby improving the efficiency of front-end engineering development. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0019] Figure 1 A flow chart of the front-end engineering construction method provided for this application;

[0020] Figure 2 A flow chart of the front-end engineering construction method provided for this application;

[0021] Figure 3 A flowchart of the front-end engineering construction method provided for this application;

[0022] Figure 4 A flowchart of the front-end engineering construction method provided for this application;

[0023] Figure 5 A flow chart of the front-end engineering construction method provided for this application;

[0024] Figure 6 A flowchart of the front-end engineering construction method provided for this application;

[0025] Figure 7 A schematic diagram of the structure of the front-end engineering construction device provided for this application;

[0026] Figure 8 A schematic diagram of the structure of the electronic device provided in this application.

[0027] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0028] Here, exemplary embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application.

[0029] It should be noted that the brief description of the terms in this application is only for the convenience of understanding the embodiments described below, and is not intended to limit the embodiments of the present application. Unless otherwise specified, these terms should be understood according to their common and usual meanings. The terms "including" and "having" in the specification and claims and the above-mentioned drawings in this application and any variation thereof are intended to cover but not exclude inclusion. For example, a product or device containing a series of components is not necessarily limited to those components clearly listed, but may include other components that are not clearly listed or inherent to these products or devices. The term "module" used in this application refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic or a combination of hardware and / or software code that can perform functions related to the element.

[0030] Front-end engineering refers to building interfaces and functions that users interact directly with in the browser through a series of technologies and tools. It not only involves code writing, but also includes performance optimization, automated construction, cross-platform compatibility, security assurance, and user experience design. The process of front-end engineering from scaffolding to application formation usually includes the following steps: First, developers use general scaffolding tools to quickly generate the basic structure of the project. Then, various components and functional modules are added according to specific needs. However, in actual development, as requirements change and functions increase, developers often need to adjust and expand the initial scaffolding structure. In addition, there are repeated construction steps in the construction process of multiple front-end projects, which not only wastes resources, but may also lead to problems such as version inconsistency. Therefore, the current front-end engineering construction solution has problems with development efficiency.

[0031] The technical content provided by this application is intended to solve the above-mentioned technical problems of related technologies. In the front-end engineering construction method, device, equipment, medium and product provided by this application, a construction request including the identification of the target prototype version is received, and a first interface including component information is provided according to a first configuration file; a second interface is provided according to the first component selected by the user in the first interface, and the target component of the corresponding version is determined according to the first version selected by the user in the second interface; according to the first configuration file, the obtained scaffolding and target components are placed in the construction directory for code integration to build the front-end engineering. The scheme of this application determines the target prototype version representing a specific scaffolding structure according to the construction request, and the first configuration file includes the components that can be carried and the versions of the components, and receives user requirements through an interactive interface, realizing the automated process of demand reception and engineering construction and reducing repetitive configurations, thereby improving the efficiency of front-end engineering development.

[0032] The technical content of this application can be used to quickly build a basic framework for front-end engineering in scenarios such as securities brokerage, investment banking, and asset management. The framework may include modules such as user login, account management, and trading interface to build a user-friendly online trading or online display platform.

[0033] The technical solutions of the present application and the technical solutions of the present application are described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. In the description of the present application, unless otherwise clearly specified and limited, each term should be understood in a broad sense in the art. The embodiments of the present application will be described below in conjunction with the accompanying drawings.

[0034] Embodiment 1

[0035] Figure 1 A schematic diagram of a front-end engineering construction method is shown in FIG. 1 . The execution subject of this example may be a front-end engineering construction device, such as Figure 1 As shown, the method includes:

[0036] Step 101: receiving a build request, the build request including an identifier of a target prototype version;

[0037] Step 102: providing a first interface according to the first configuration file, the first interface including component information under the target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of scaffolds corresponding to each prototype version; different prototype versions correspond to different scaffolds;

[0038] Step 103: providing a second interface according to the first component selected by the user in the first interface, and determining the target component of the corresponding version according to the first version selected by the user in the second interface; wherein the second interface includes the version range of the first component; and obtaining the scaffolding and target component corresponding to the target prototype version according to the first configuration file;

[0039] Step 104: Place the scaffolding and target components corresponding to the target prototype version into the build directory for code integration to build a front-end project.

[0040] In practical applications, the executor of the method can be a front-end engineering construction device, and there are many ways to implement it. For example, it can be implemented through a computer program, such as application software, etc.; or, it can be implemented as a medium storing relevant computer programs, such as a USB flash drive, a cloud disk, etc.; or, it can be implemented through a physical device that integrates or installs relevant computer programs, such as a chip, etc.

[0041] Exemplarily, a build operation can be received through a user's interface click operation or an interface service provided by the execution subject, and the identifier of the target prototype version of the build operation can be one or more to start the construction of one or more front-end projects. In this example, the prototype version is used to indicate the structure of the scaffolding, wherein the prototype version specifies the directory structure, coding style, configuration files, and underlying dependencies of the scaffolding. For example, the scaffolding corresponding to different prototype versions is differentiated in one or more dimensions such as directory structure, coding style, configuration files, and underlying dependencies. Specifically, the prototype version is a description file of the scaffolding corresponding to the prototype version. It should be noted that after receiving the build request, a file path must be determined, and the file path is used to store all files of the front-end project.

[0042] After obtaining the build request, a first interface including component information under the target prototype version is provided according to the first configuration file. In practical applications, the first configuration file may be a file in .json format; when it is necessary to obtain data under the first configuration file, the first configuration file needs to be parsed. The first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of the scaffolding corresponding to each prototype version. Exemplarily, the component information represents the component information of all components that can be carried on the scaffolding corresponding to the target prototype version, wherein the component may be any one or a combination of any of the functional modules, UI components, and third-party dependencies. In practical applications, the component information may include a description of the function and purpose of each component, as well as a description of all versions of components under each component. For example, the first interface may include: component A, used to implement function 1; component B, used to implement function 2; the user may click or check in the selection provided in the first interface to select the first component according to the component information. It should be noted that the first component represents the component selected by the user and is not used to limit the number or type of components. Further, a second interface is provided according to the first component selected by the user on the first interface, and the target component of the corresponding version is determined according to the first version selected by the user on the second interface. Among them, the second interface includes a version range of the first component, which represents the version compatible with the scaffold, that is, the version corresponding to the first component that can be mounted on the scaffold corresponding to the target prototype version. In practical applications, a default item can also be set in the version range of the first component displayed on the second interface, and the default item is used for the rapid construction of the front-end project in the scenario where the user does not limit the first version range or the user does not make a selection on the second interface. After determining the target component, the scaffold and target component corresponding to the target prototype version are obtained according to the first configuration file. Specifically, the scaffold and target component corresponding to the target prototype version are obtained according to the coordinates of the scaffold corresponding to the target prototype version and the component coordinates of the target component. In practical applications, the coordinates can be used for positioning in a local database or an open source community, and the scaffold and target component corresponding to the target prototype version are downloaded after positioning. After obtaining the scaffold and target component corresponding to the target prototype version, the scaffold and target component corresponding to the target prototype version are placed in the build directory for code integration to build the front-end project. The front-end engineering construction method of this example separates the development stage and the demand stage; in the development stage, it is necessary to establish multiple prototype versions and scaffolding corresponding to the prototype versions, multiple components that can be installed under the prototype version, and the version of each component; in the demand stage, the user's needs are obtained through interaction with the user interface. The solution of this example improves the utilization of resources through the data in the first configuration file, avoids the problem of incompatibility between components and scaffolding through version control, and avoids the inefficiency of development based on demand, thereby realizing the rapid construction of the front-end engineering.

[0043] In the front-end engineering construction method of this example, a construction request including an identifier of a target prototype version is received, and a first interface including component information is provided according to a first configuration file; a second interface is provided according to a first component selected by a user in the first interface, and a target component of a corresponding version is determined according to a first version selected by the user in the second interface; according to the first configuration file, the obtained scaffolding and target components are placed in a construction directory for code integration to build a front-end engineering. The scheme of the present application determines the target prototype version representing a specific scaffolding structure according to a construction request, and the first configuration file includes components that can be installed and versions of the components, and receives user requirements through an interactive interface, thereby realizing an automated process of requirement reception and engineering construction and reducing repetitive configurations, thereby improving the efficiency of front-end engineering development.

[0044] As yet another example, the target component includes a basic target component; and the first interface includes basic component information under a target prototype version.

[0045] In this example, basic components represent independent components that can realize basic functions in front-end engineering. For example, the UI display function corresponds to basic component A, the state management function corresponds to component B, and the routing management function corresponds to component C. In this example, by selecting multiple basic target components, modular management of components can be achieved, and the efficiency of building front-end engineering can be improved.

[0046] Figure 2 A schematic diagram of a front-end engineering construction method is shown in FIG. Figure 2 As shown, the target component also includes dependent target components; the front-end engineering construction method also includes:

[0047] Step 201: If the currently determined target component is a basic component, a third interface is provided, the third interface including component information of dependent components that depend on the target component;

[0048] Step 202: provide a fourth interface according to the second component selected by the user in the third interface, the fourth interface including the version range of the second component; determine the component of the corresponding version according to the second version selected by the user in the fourth interface and add it to the target component.

[0049] In this example, different components are usually required to realize complex functions. For the version selection of dependent components that depend on the basic component, it is necessary to determine it after the version of the basic component is determined. If the currently determined target component is the basic component, a third interface is provided, and the third interface includes component information of dependent components that depend on the target component. Exemplarily, the third interface can be a new interface to which the user jumps after selecting the version of the basic component in the second interface. Optionally, the third interface can still be the second interface; wherein the component information of the dependent component is hidden in the second interface, and after the user selects the version of the basic component, the component information of the dependent component that depends on the selected basic component is changed from hidden to displayed. A fourth interface is provided according to the second component selected by the user in the third interface, and the fourth interface includes the version range of the second component; according to the second version selected by the user in the fourth interface, the component of the corresponding version is determined and added to the target component. In this example, the second component represents the dependent component selected by the user, and the fourth interface includes the version range of the dependent component selected by the user. In actual applications, when users are required to select multiple basic components and multiple dependent components, one interface switching method is to select a basic component and determine the version, and then select the dependent component corresponding to the basic component and determine the version; select another basic component and determine the version, and then select the dependent component corresponding to another basic component and determine the version; this solution can improve the logic of interface switching. Optionally, another interface switching method is that the user selects multiple basic components according to needs, and then selects multiple dependent components corresponding to the multiple basic components and determines the versions; this solution can reduce repeated selection of dependent components and version conflicts when a dependent component depends on multiple basic components. The solution in this example can avoid the problem of incompatible versions of dependent components by selecting the version of the basic component and then selecting the corresponding version of the dependent component.

[0050] As yet another example, each scaffold and each version component is stored in a package management platform; Figure 3 A schematic diagram of a front-end engineering construction method is shown in FIG. Figure 3 As shown, in step 103, according to the first configuration file, the scaffolding and target components corresponding to the target prototype version are obtained, including:

[0051] Step 301: Send a download request to the package management platform, where the download request includes the coordinates of the scaffold corresponding to the target prototype version and the coordinates of the target component;

[0052] Step 302: Receive the scaffolding and target components corresponding to the target prototype version returned by the package management platform.

[0053] In actual applications, before sending a download request to the package management platform, the data in the first configuration file and the package management platform can be updated to ensure data synchronization between the two. The solution of this example can reduce the load of the essential subject and increase the speed of downloading the scaffolding and target components corresponding to the target prototype version by sending a download request to the package management platform and receiving the scaffolding and target components corresponding to the target prototype version returned by the package management platform.

[0054] As another example, the front-end engineering construction method also includes:

[0055] A second configuration file is maintained, where the second configuration file includes project information of each front-end project, where the project information includes historical operations of prototype versions, scaffolds, and components under the front-end project.

[0056] Exemplarily, when the front-end project is created, a unique front-end project identifier is generated, and a corresponding record is created in the second configuration file; whenever an operation such as adding, deleting, or updating occurs on a prototype version, scaffolding, or component, detailed information of the operation such as timestamp, operation type, and operation content is added to the component history operation field. Optionally, an interface for querying and retrieving project information can also be designed, allowing users to query by conditions such as the front-end project identifier, prototype version, scaffolding, and historical operations of components. In the solution of this example, project information can be recorded through the second configuration file, and the second configuration file can also be used to support version rollback and coexistence of multiple versions of the front-end project.

[0057] As another example, Figure 4 A schematic diagram of a front-end engineering construction method is shown in FIG. Figure 4 As shown, the front-end engineering construction method also includes:

[0058] Step 401, receiving a component addition requirement, where the component addition requirement is used to add a component under a first front-end project;

[0059] Step 402: Determine the prototype version of the first front-end project and the version components currently included according to the second configuration file, and provide a fifth interface according to the first configuration file; the fifth interface includes component information under the prototype version of the first front-end project except for the version components currently included in the first front-end project;

[0060] Step 403: providing a sixth interface according to the newly added component selected by the user in the fifth interface, and determining a target newly added component according to the third version selected by the user in the sixth interface; wherein the sixth interface includes a version range of the newly added component;

[0061] Step 404: Obtain the target new component according to the coordinates of the target new component in the first configuration file, and place the target new component in the build directory of the first front-end project for code integration.

[0062] The component addition requirement in this example may include a project identifier, which is used to add components under the first front-end project. Optionally, the determination of the first front-end project may also provide an interface to the user and be obtained by receiving the user's selection. After obtaining the component addition requirement, the prototype version of the first front-end project and the version components currently included are determined according to the second configuration file. Specifically, the current prototype version of the first front-end project and the version components currently included are determined according to the historical operations of the prototype version, scaffolding and components in the second configuration file. In practical applications, the above information can be obtained by establishing a corresponding identifier and performing corresponding operations on the identifier according to the historical operations of the prototype version, scaffolding and components in the second configuration file. Further, according to the first configuration file, a fifth interface is provided; the fifth interface includes component information other than the version components currently included in the first front-end project under the prototype version of the first front-end project; according to the newly added components selected by the user in the fifth interface, a sixth interface is provided, and the target newly added components are determined according to the third version selected by the user in the sixth interface; wherein the sixth interface includes the version range of the newly added components. For example, according to the first configuration file, the first interface displays the information of components A, B, and C under the prototype version, and through the second configuration file, it can be known that the currently included version component is component A of version 1.0, then the fifth interface includes component information of components B and C, and the sixth interface can be the version range of component B or component C according to the user's selection. In a possible implementation, the fifth interface can be the first interface in which the component information corresponding to the currently included version component is in an unselectable state, and the corresponding sixth interface is the corresponding second interface; taking the above example, the fifth interface is the first interface that displays content including component A as unselectable, component B as optional, and component C as optional. After obtaining the target newly added component, the target newly added component is obtained according to the coordinates of the target newly added component in the first configuration file, and the target newly added component is placed in the construction directory of the first front-end project for code integration. The solution of this example, based on the component addition requirements, provides the fifth and sixth interfaces through the first and second configuration files, realizes the addition of components to the front-end project, and improves the flexibility of the front-end project construction.

[0063] As another example, Figure 5 A schematic diagram of a front-end engineering construction method is shown in FIG. Figure 5 As shown, the front-end engineering construction method also includes:

[0064] Step 501: receiving a component update requirement, where the component update requirement is used to update a component under a second front-end project;

[0065] Step 502: Determine the prototype version and the version components currently included in the second front-end project according to the second configuration file, and provide a seventh interface according to the first configuration file; the seventh interface includes component information of the version components currently included in the second front-end project;

[0066] Step 503: providing an eighth interface according to the update component selected by the user in the seventh interface, and determining a target update component according to the fourth version selected by the user in the eighth interface; wherein the eighth interface includes a version range of the update component except the current version under the second front-end project;

[0067] Step 504: Obtain the target update component according to the coordinates of the target update component in the first configuration file, and use the target update component to overwrite the current version component in the build directory of the second front-end project, and perform code integration.

[0068] Exemplarily, there is no sequential relationship between the component update request and the component addition request, but for the same front-end project, both the component update request and the component addition request should be after the build request. The component update request in this example may include a project identifier for updating the component under the second front-end project. Optionally, the determination of the second front-end project may also provide an interface to the user and be obtained by receiving the user's selection. After obtaining the component update request, the prototype version of the second front-end project and the currently included version components are determined according to the second configuration file. Specifically, the current prototype version of the second front-end project and the currently included version components are determined according to the historical operations of the prototype version, scaffolding and components in the second configuration file. In actual applications, the above information can be obtained by establishing a corresponding identifier and performing corresponding operations on the identifier according to the historical operations of the prototype version, scaffolding and components in the second configuration file. Further, according to the first configuration file, a seventh interface is provided; the seventh interface includes component information of the version components currently included under the prototype version of the second front-end project; according to the update component selected by the user in the seventh interface, an eighth interface is provided, and the target update component is determined according to the fourth version selected by the user in the eighth interface; wherein the eighth interface includes the version range of the update component except the current version under the second front-end project. For example, according to the first configuration file, the first interface displays the information of components A, B, and C under the prototype version, and through the second configuration file, it can be known that the currently included version component is the 1.0 version of component A, then the seventh interface includes the component information of component A, and the eighth interface includes the version range of component A except 1.0. In a possible implementation, the seventh interface can be the first interface where the component information corresponding to the version component not currently included is in an unselectable state, and the corresponding eighth interface is the second interface where the version corresponding to the corresponding currently included version component is in an unselectable state. Taking the above example, the seventh interface is the first interface where the display content includes component A as optional, component B as unselectable, and component C as unselectable; the eighth interface is the second interface where the display content includes component A as 1.0 as unselectable, and component A as a version range except 1.0 as optional. After obtaining the target update component, the target update component is obtained according to the coordinates of the target update component in the first configuration file, and the target update component is used to overwrite the current version component under the build directory of the second front-end project, and code integration is performed. The solution of this example, based on the component update requirement, provides the seventh interface and the eighth interface through the first configuration file and the second configuration file, thereby realizing the component update of the front-end project and improving the flexibility of the front-end project construction.

[0069] As another example, Figure 6 A schematic diagram of a front-end engineering construction method is shown in FIG. Figure 6 As shown, after receiving the build request in step 101, the following steps are also included:

[0070] Step 601: Push the construction template information of the target prototype version, where the construction template information includes the target component corresponding to the target prototype version during the historical construction;

[0071] Step 602: Build the front-end project according to the building template selected by the user.

[0072] Exemplarily, the construction template information of the target prototype version can be pushed through an interface; specifically, the interface can be a first interface including component information under the target prototype version and the construction template information of the target prototype version; optionally, the interface can be a new interface that is jumped to by clicking in the first interface. Exemplarily, the target component corresponding to the target prototype version in the construction template information during the historical construction, for example, the construction template information can be the target component corresponding to the target prototype during the first construction; or the construction template information can be the target component modified on the basis of the target component corresponding to the target prototype during the first construction. After obtaining the construction template selected by the user, the front-end project is constructed according to the construction template selected by the user. The solution of this example reduces user interaction by constructing a template, which can improve the efficiency of front-end project construction.

[0073] The front-end engineering construction method provided in the embodiment of the present application receives a construction request including an identifier of a target prototype version, and provides a first interface including component information according to a first configuration file; provides a second interface according to a first component selected by a user in the first interface, and determines a target component of a corresponding version according to a first version selected by the user in the second interface; and places the obtained scaffolding and target components in a construction directory for code integration according to the first configuration file to build a front-end engineering. The scheme of the present application determines a target prototype version representing a specific scaffolding structure according to a construction request, and the first configuration file includes components that can be loaded and versions of the components, and receives user requirements through an interactive interface, thereby realizing an automated process of receiving requirements and engineering construction and reducing repetitive configurations, thereby improving the efficiency of front-end engineering development.

[0074] Embodiment 2

[0075] Figure 7 A schematic diagram of the structure of the front-end engineering construction device provided for this application, such as Figure 7 As shown, the front-end engineering construction device 70 provided in this embodiment includes:

[0076] A receiving module 701 is used to receive a build request, where the build request includes an identifier of a target prototype version;

[0077] A providing module 702 is used to provide a first interface according to a first configuration file, wherein the first interface includes component information under a target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of a scaffold corresponding to each prototype version; different prototype versions correspond to different scaffold structures;

[0078] The obtaining module 703 is used to provide a second interface according to the first component selected by the user in the first interface, and determine the target component of the corresponding version according to the first version selected by the user in the second interface; wherein the second interface includes the version range of the first component; and obtain the scaffolding and target component corresponding to the target prototype version according to the first configuration file;

[0079] The construction module 704 is used to place the scaffolding and target components corresponding to the target prototype version into the construction directory for code integration to build the front-end project.

[0080] In practical applications, there are many ways to implement the front-end engineering construction device. For example, it can be implemented through a computer program, such as application software, etc.; or it can be implemented as a medium storing relevant computer programs, such as a USB flash drive, a cloud disk, etc.; or it can be implemented through a physical device that integrates or installs relevant computer programs, such as a chip.

[0081] Exemplarily, a build operation can be received through a user's interface click operation or an interface service provided by the execution subject, and the identifier of the target prototype version of the build operation can be one or more to start the construction of one or more front-end projects. In this example, the prototype version is used to indicate the structure of the scaffolding, wherein the prototype version specifies the directory structure, coding style, configuration files, and underlying dependencies of the scaffolding. For example, the scaffolding corresponding to different prototype versions is differentiated in one or more dimensions such as directory structure, coding style, configuration files, and underlying dependencies. Specifically, the prototype version is a description file of the scaffolding corresponding to the prototype version. It should be noted that after receiving the build request, a file path must be determined, and the file path is used to store all files of the front-end project.

[0082] After obtaining the build request, a first interface including component information under the target prototype version is provided according to the first configuration file. In practical applications, the first configuration file may be a file in .json format; when it is necessary to obtain data under the first configuration file, the first configuration file needs to be parsed. The first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of the scaffolding corresponding to each prototype version. Exemplarily, the component information represents the component information of all components that can be carried on the scaffolding corresponding to the target prototype version, wherein the component may be any one or a combination of any of the functional modules, UI components, and third-party dependencies. In practical applications, the component information may include a description of the function and purpose of each component, as well as a description of all versions of components under each component. For example, the first interface may include: component A, used to implement function 1; component B, used to implement function 2; the user may click or check in the selection provided in the first interface to select the first component according to the component information. It should be noted that the first component represents the component selected by the user and is not used to limit the number or type of components. Further, a second interface is provided according to the first component selected by the user on the first interface, and the target component of the corresponding version is determined according to the first version selected by the user on the second interface. Among them, the second interface includes a version range of the first component, which represents the version compatible with the scaffold, that is, the version corresponding to the first component that can be mounted on the scaffold corresponding to the target prototype version. In practical applications, a default item can also be set in the version range of the first component displayed on the second interface, and the default item is used for the rapid construction of the front-end project in the scenario where the user does not limit the first version range or the user does not make a selection on the second interface. After determining the target component, the scaffold and target component corresponding to the target prototype version are obtained according to the first configuration file. Specifically, the scaffold and target component corresponding to the target prototype version are obtained according to the coordinates of the scaffold corresponding to the target prototype version and the component coordinates of the target component. In practical applications, the coordinates can be used for positioning in a local database or an open source community, and the scaffold and target component corresponding to the target prototype version are downloaded after positioning. After obtaining the scaffold and target component corresponding to the target prototype version, the scaffold and target component corresponding to the target prototype version are placed in the build directory for code integration to build the front-end project. The front-end engineering construction of this example separates the development stage and the demand stage; in the development stage, it is necessary to establish multiple prototype versions and scaffolding corresponding to the prototype versions, multiple components that can be installed under the prototype version, and the version of each component; in the demand stage, the user's needs are obtained through interaction with the user interface. The solution of this example improves the utilization of resources through the data in the first configuration file, avoids the problem of incompatibility between components and scaffolding through version control, and avoids the inefficiency of development based on demand, thereby realizing the rapid construction of the front-end engineering.

[0083] In the front-end engineering construction device of this example, a construction request including an identifier of a target prototype version is received, and a first interface including component information is provided according to a first configuration file; a second interface is provided according to a first component selected by a user in the first interface, and a target component of a corresponding version is determined according to a first version selected by the user in the second interface; according to the first configuration file, the obtained scaffolding and target components are placed in a construction directory for code integration to build a front-end engineering. The scheme of the present application determines the target prototype version representing a specific scaffolding structure according to a construction request, and the first configuration file includes components that can be installed and versions of the components, and receives user requirements through an interactive interface, thereby realizing an automated process of receiving requirements and engineering construction and reducing repetitive configurations, thereby improving the efficiency of front-end engineering development.

[0084] In a possible implementation, the target component includes a basic target component; and the first interface includes basic component information under the target prototype version.

[0085] In this example, basic components represent independent components that can realize basic functions in front-end engineering. For example, the UI display function corresponds to basic component A, the state management function corresponds to component B, and the routing management function corresponds to component C. In this example, by selecting multiple basic target components, modular management of components can be achieved, and the efficiency of building front-end engineering can be improved.

[0086] In a possible implementation, the target component also includes a dependent target component; and the obtaining module 703 is further used to:

[0087] If the currently determined target component is a basic component, a third interface is provided, the third interface including component information of dependent components that depend on the target component;

[0088] A fourth interface is provided according to the second component selected by the user in the third interface, and the fourth interface includes the version range of the second component; according to the second version selected by the user in the fourth interface, a component of a corresponding version is determined and added to the target component.

[0089] In this example, different components are usually required to realize complex functions. For the version selection of dependent components that depend on the basic component, it is necessary to determine it after the version of the basic component is determined. If the currently determined target component is the basic component, a third interface is provided, and the third interface includes component information of dependent components that depend on the target component. Exemplarily, the third interface can be a new interface to which the user jumps after selecting the version of the basic component in the second interface. Optionally, the third interface can still be the second interface; wherein the component information of the dependent component is hidden in the second interface, and after the user selects the version of the basic component, the component information of the dependent component that depends on the selected basic component is changed from hidden to displayed. A fourth interface is provided according to the second component selected by the user in the third interface, and the fourth interface includes the version range of the second component; according to the second version selected by the user in the fourth interface, the component of the corresponding version is determined and added to the target component. In this example, the second component represents the dependent component selected by the user, and the fourth interface includes the version range of the dependent component selected by the user. In actual applications, when users are required to select multiple basic components and multiple dependent components, one interface switching method is to select a basic component and determine the version, and then select the dependent component corresponding to the basic component and determine the version; select another basic component and determine the version, and then select the dependent component corresponding to another basic component and determine the version; this solution can improve the logic of interface switching. Optionally, another interface switching method is that the user selects multiple basic components according to needs, and then selects multiple dependent components corresponding to the multiple basic components and determines the versions; this solution can reduce repeated selection of dependent components and version conflicts when a dependent component depends on multiple basic components. The solution in this example can avoid the problem of incompatible versions of dependent components by selecting the version of the basic component and then selecting the corresponding version of the dependent component.

[0090] In a possible implementation, the obtaining module 703 is specifically configured to:

[0091] Send a download request to the package management platform, the download request includes the coordinates of the scaffolding corresponding to the target prototype version and the coordinates of the target component;

[0092] Receive the scaffolding and target components corresponding to the target prototype version returned by the package management platform.

[0093] In actual applications, before sending a download request to the package management platform, the data in the first configuration file and the package management platform can be updated to ensure data synchronization between the two. The solution of this example can reduce the load of the essential subject and increase the speed of downloading the scaffolding and target components corresponding to the target prototype version by sending a download request to the package management platform and receiving the scaffolding and target components corresponding to the target prototype version returned by the package management platform.

[0094] In a possible implementation, the front-end engineering construction device further includes a maintenance module 705; the maintenance module 705 is specifically used to:

[0095] A second configuration file is maintained, where the second configuration file includes project information of each front-end project, where the project information includes historical operations of prototype versions, scaffolds, and components under the front-end project.

[0096] Exemplarily, when the front-end project is created, a unique front-end project identifier is generated, and a corresponding record is created in the second configuration file; whenever an operation such as adding, deleting, or updating occurs on a prototype version, scaffolding, or component, detailed information of the operation such as timestamp, operation type, and operation content is added to the component history operation field. Optionally, an interface for querying and retrieving project information can also be designed, allowing users to query by conditions such as the front-end project identifier, prototype version, scaffolding, and historical operations of components. In the solution of this example, project information can be recorded through the second configuration file, and the second configuration file can also be used to support version rollback and coexistence of multiple versions of the front-end project.

[0097] In a possible implementation, the maintenance module 705 is further configured to:

[0098] Receive new component requirements, which are used to add components under the first front-end project;

[0099] Determine the prototype version of the first front-end project and the version components currently included according to the second configuration file, and provide a fifth interface according to the first configuration file; the fifth interface includes component information under the prototype version of the first front-end project except for the version components currently included in the first front-end project;

[0100] Providing a sixth interface according to the newly added component selected by the user on the fifth interface, and determining a target newly added component according to the third version selected by the user on the sixth interface; wherein the sixth interface includes a version range of the newly added component;

[0101] According to the coordinates of the target new component in the first configuration file, the target new component is obtained, and the target new component is placed in the build directory of the first front-end project for code integration.

[0102] The component addition requirement in this example may include a project identifier, which is used to add components under the first front-end project. Optionally, the determination of the first front-end project may also provide an interface to the user and be obtained by receiving the user's selection. After obtaining the component addition requirement, the prototype version of the first front-end project and the version components currently included are determined according to the second configuration file. Specifically, the current prototype version of the first front-end project and the version components currently included are determined according to the historical operations of the prototype version, scaffolding and components in the second configuration file. In practical applications, the above information can be obtained by establishing a corresponding identifier and performing corresponding operations on the identifier according to the historical operations of the prototype version, scaffolding and components in the second configuration file. Further, according to the first configuration file, a fifth interface is provided; the fifth interface includes component information other than the version components currently included in the first front-end project under the prototype version of the first front-end project; according to the newly added components selected by the user in the fifth interface, a sixth interface is provided, and the target newly added components are determined according to the third version selected by the user in the sixth interface; wherein the sixth interface includes the version range of the newly added components. For example, according to the first configuration file, the first interface displays the information of components A, B, and C under the prototype version, and through the second configuration file, it can be known that the currently included version component is component A of version 1.0, then the fifth interface includes component information of components B and C, and the sixth interface can be the version range of component B or component C according to the user's selection. In a possible implementation, the fifth interface can be the first interface in which the component information corresponding to the currently included version component is in an unselectable state, and the corresponding sixth interface is the corresponding second interface; taking the above example, the fifth interface is the first interface that displays content including component A as unselectable, component B as optional, and component C as optional. After obtaining the target newly added component, the target newly added component is obtained according to the coordinates of the target newly added component in the first configuration file, and the target newly added component is placed in the construction directory of the first front-end project for code integration. The solution of this example, based on the component addition requirements, provides the fifth and sixth interfaces through the first and second configuration files, realizes the addition of components to the front-end project, and improves the flexibility of the front-end project construction.

[0103] In a possible implementation, the maintenance module 705 is further configured to:

[0104] Receive component update requirements, which are used to update components under the second front-end project;

[0105] Determine the prototype version and the version components currently included in the second front-end project according to the second configuration file, and provide a seventh interface according to the first configuration file; the seventh interface includes component information of the version components currently included in the second front-end project;

[0106] According to the update component selected by the user in the seventh interface, an eighth interface is provided, and according to the fourth version selected by the user in the eighth interface, a target update component is determined; wherein the eighth interface includes a version range of the update component except the current version under the second front-end project;

[0107] According to the coordinates of the target update component in the first configuration file, the target update component is obtained, and the current version component in the build directory of the second front-end project is overwritten with the target update component, and code integration is performed.

[0108] Exemplarily, there is no sequential relationship between the component update request and the component addition request, but for the same front-end project, both the component update request and the component addition request should be after the build request. The component update request in this example may include a project identifier for updating the component under the second front-end project. Optionally, the determination of the second front-end project may also provide an interface to the user and be obtained by receiving the user's selection. After obtaining the component update request, the prototype version of the second front-end project and the currently included version components are determined according to the second configuration file. Specifically, the current prototype version of the second front-end project and the currently included version components are determined according to the historical operations of the prototype version, scaffolding and components in the second configuration file. In actual applications, the above information can be obtained by establishing a corresponding identifier and performing corresponding operations on the identifier according to the historical operations of the prototype version, scaffolding and components in the second configuration file. Further, according to the first configuration file, a seventh interface is provided; the seventh interface includes component information of the version components currently included under the prototype version of the second front-end project; according to the update component selected by the user in the seventh interface, an eighth interface is provided, and the target update component is determined according to the fourth version selected by the user in the eighth interface; wherein the eighth interface includes the version range of the update component except the current version under the second front-end project. For example, according to the first configuration file, the first interface displays the information of components A, B, and C under the prototype version, and through the second configuration file, it can be known that the currently included version component is the 1.0 version of component A, then the seventh interface includes the component information of component A, and the eighth interface includes the version range of component A except 1.0. In a possible implementation, the seventh interface can be the first interface where the component information corresponding to the version component not currently included is in an unselectable state, and the corresponding eighth interface is the second interface where the version corresponding to the corresponding currently included version component is in an unselectable state. Taking the above example, the seventh interface is the first interface where the display content includes component A as optional, component B as unselectable, and component C as unselectable; the eighth interface is the second interface where the display content includes component A as 1.0 as unselectable, and component A as a version range except 1.0 as optional. After obtaining the target update component, the target update component is obtained according to the coordinates of the target update component in the first configuration file, and the target update component is used to overwrite the current version component under the build directory of the second front-end project, and code integration is performed. The solution of this example, based on the component update requirement, provides the seventh interface and the eighth interface through the first configuration file and the second configuration file, thereby realizing the component update of the front-end project and improving the flexibility of the front-end project construction.

[0109] In a possible implementation, the receiving module 701 is further configured to:

[0110] Push the build template information of the target prototype version, where the build template information includes the target component corresponding to the target prototype version in the historical build;

[0111] Build the front-end project according to the build template selected by the user.

[0112] Exemplarily, the construction template information of the target prototype version can be pushed through an interface; specifically, the interface can be a first interface including component information under the target prototype version and the construction template information of the target prototype version; optionally, the interface can be a new interface that is jumped to by clicking in the first interface. Exemplarily, the target component corresponding to the target prototype version in the construction template information during the historical construction, for example, the construction template information can be the target component corresponding to the target prototype during the first construction; or the construction template information can be the target component modified on the basis of the target component corresponding to the target prototype during the first construction. After obtaining the construction template selected by the user, the front-end project is constructed according to the construction template selected by the user. The solution of this example reduces user interaction by constructing a template, which can improve the efficiency of front-end project construction.

[0113] The front-end engineering construction device provided in the embodiment of the present application provides a first interface including component information according to a first configuration file by receiving a construction request including an identification of a target prototype version; provides a second interface according to a first component selected by a user in the first interface, and determines a target component of a corresponding version according to a first version selected by the user in the second interface; and places the obtained scaffolding and target components in a construction directory for code integration according to the first configuration file to build a front-end engineering. The scheme of the present application determines a target prototype version representing a specific scaffolding structure according to a construction request, and the first configuration file includes components that can be loaded and versions of the components, and receives user requirements through an interactive interface, thereby realizing an automated process of receiving requirements and engineering construction and reducing repetitive configurations, thereby improving the efficiency of front-end engineering development.

[0114] Figure 8 This is a schematic diagram of the structure of the electronic device provided in this application. Figure 8 As shown, the electronic device 50 provided in this embodiment includes: at least one processor 501 and a memory 502. Optionally, the device 50 also includes a communication component 503. The processor 501, the memory 502 and the communication component 503 are connected via a bus 504.

[0115] In a specific implementation process, at least one processor 501 executes the computer-executable instructions stored in the memory 502, so that at least one processor 501 executes the above method.

[0116] The specific implementation process of the processor 501 can be found in the above method embodiment, and its implementation principle and technical effect are similar, so this embodiment will not be repeated here.

[0117] In the above embodiments, it should be understood that the processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. A general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the invention may be directly implemented as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the processor.

[0118] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (Non-volatile Memory, NVM), such as at least one disk memory.

[0119] The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of the present application is not limited to only one bus or one type of bus.

[0120] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0121] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0122] The above-mentioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0123] An exemplary readable storage medium is coupled to a processor so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0124] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0125] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0126] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0127] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0128] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, disk or optical disk and other media that can store program codes.

[0129] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A front-end engineering construction method, characterized in that: include: receiving a build request, the build request including an identification of a target prototype version; According to the first configuration file, a first interface is provided, wherein the first interface includes component information under the target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of scaffolds corresponding to each prototype version; different prototype versions correspond to different scaffolds; Providing a second interface according to the first component selected by the user in the first interface, and determining a target component of a corresponding version according to the first version selected by the user in the second interface; wherein the second interface includes a version range of the first component; obtaining a scaffold and the target component corresponding to the target prototype version according to the first configuration file; The scaffolding corresponding to the target prototype version and the target component are placed in the build directory for code integration to build a front-end project.

2. The method according to claim 1, characterized in that: The target component includes a basic target component; the first interface includes basic component information under a target prototype version.

3. The method according to claim 2, characterized in that The target component also includes a dependent target component; the method also includes: If the currently determined target component is a basic component, providing a third interface, the third interface including component information of dependent components that depend on the target component; A fourth interface is provided according to the second component selected by the user in the third interface, wherein the fourth interface includes the version range of the second component; and a component of a corresponding version is determined according to the second version selected by the user in the fourth interface and added to the target component.

4. The method according to claim 1, characterized in that: Each scaffold and each version component is stored in a package management platform; the scaffold and the target component corresponding to the target prototype version are obtained according to the first configuration file, including: Sending a download request to the package management platform, the download request including the coordinates of the scaffold corresponding to the target prototype version and the coordinates of the target component; Receive the scaffolding and the target component corresponding to the target prototype version returned by the package management platform.

5. The method according to claim 1, characterized in that The method further comprises: Maintain a second configuration file, wherein the second configuration file includes project information of each front-end project, and the project information includes historical operations of prototype versions, scaffolds, and components under the front-end project.

6. The method according to claim 5, characterized in that The method further comprises: receiving a component addition requirement, wherein the component addition requirement is used to add a component under the first front-end project; Determine the prototype version and the version components currently included in the first front-end project according to the second configuration file, and provide a fifth interface according to the first configuration file; the fifth interface includes component information under the prototype version of the first front-end project except for the version components currently included in the first front-end project; According to the newly added component selected by the user on the fifth interface, a sixth interface is provided, and according to the third version selected by the user on the sixth interface, a target newly added component is determined; wherein the sixth interface includes a version range of the newly added component; According to the coordinates of the target new component in the first configuration file, the target new component is obtained, and the target new component is placed in the construction directory of the first front-end project for code integration.

7. The method according to claim 5, characterized in that The method further comprises: receiving a component update requirement, wherein the component update requirement is used to update a component under the second front-end project; Determine the prototype version and the version components currently included in the second front-end project according to the second configuration file, and provide a seventh interface according to the first configuration file; the seventh interface includes component information of the version components currently included in the second front-end project; providing an eighth interface according to the update component selected by the user on the seventh interface, and determining a target update component according to the fourth version selected by the user on the eighth interface; wherein the eighth interface includes a version range of the update component except the current version under the second front-end project; According to the coordinates of the target update component in the first configuration file, the target update component is obtained, and the current version component in the build directory of the second front-end project is overwritten with the target update component, and code integration is performed.

8. The method according to any one of claims 1 to 7, characterized in that: After receiving the construction request, the method further includes: Pushing the construction template information of the target prototype version, wherein the construction template information includes the target component corresponding to the target prototype version during the historical construction; Build the front-end project according to the build template selected by the user.

9. A front-end engineering construction device, characterized in that: include: A receiving module, configured to receive a build request, wherein the build request includes an identifier of a target prototype version; A providing module is used to provide a first interface according to a first configuration file, wherein the first interface includes component information under the target prototype version; wherein the first configuration file includes component information under each prototype version, component coordinates of each version component, and coordinates of scaffolds corresponding to each prototype version; different prototype versions correspond to different scaffolds. an acquisition module, configured to provide a second interface according to the first component selected by the user in the first interface, and determine a target component of a corresponding version according to the first version selected by the user in the second interface; wherein the second interface includes a version range of the first component; and obtain a scaffold and the target component corresponding to the target prototype version according to the first configuration file; The construction module is used to place the scaffolding corresponding to the target prototype version and the target component into the construction directory for code integration to build a front-end project.

10. An electronic device, characterized in that: include: Memory, processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor performs the method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 8 when executed by a processor.

12. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 8 is implemented.

Images