Multi-project integrated front-end development method and device based on scaffold

Abstract

The embodiment of the invention discloses a multi-project integrated front-end development method and device based on a scaffold. The method comprises the following steps: building a scaffold system based on a preset scaffold tool, and adding a target configuration file for managing each project in a global configuration file of the scaffold system; and when an execution instruction for any item is detected, searching an entry file in an item folder corresponding to the item based on the target configuration file, and performing an execution operation according to the entry file. According to the embodiment of the invention, a plurality of projects can use one scaffold at the same time through a sub-folder management and resource file sharing mechanism, so that the plurality of projects can be centralized in one scaffold system for management, the balance between independence and resource sharing among the projects is realized, and the development efficiency is improved.

Description

Technical Field

[0001] This specification relates to software development technology in one or more embodiments, and more particularly to a scaffold-based multi-project integrated front-end development method and apparatus. Background Technology

[0002] A scaffolding is a basic set of code and tools used to quickly initialize the basic structure of a project. It provides the essential configurations and functionalities required for project development, helping developers quickly establish the initial code structure for a new project. This allows developers to begin writing business logic more quickly without having to set up the entire project environment from scratch. Currently, the various front-end development scaffolding tools widely available in the market are designed for one project per scaffolding, resulting in fragmented projects. Similar projects cannot be centrally managed, impacting development efficiency. Summary of the Invention

[0003] To address the aforementioned issues, this specification describes one or more embodiments of a scaffold-based multi-project integrated front-end development method, apparatus, and electronic device.

[0004] According to the first aspect, a scaffolding-based multi-project integrated front-end development method is provided, the method comprising:

[0005] A scaffolding system is built based on preset scaffolding tools, and a target configuration file for managing each project is added to the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0006] When an execution instruction for any project is detected, the entry file is located in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

[0007] Preferably, the standardized reusable resources include shared general pages, general components, and general scripts, and the project resources include project routes, project pages, entry scripts, and entry pages.

[0008] Preferably, when an execution instruction for any project is detected, searching for an entry file in the project folder corresponding to the project based on the target configuration file, and performing the execution operation according to the entry file, includes:

[0009] When an execution instruction for any project is detected, the metadata file of the project is invoked, and the project name and the target configuration file corresponding to the project are determined based on the metadata file.

[0010] The project folder corresponding to the project is determined based on the project name, and the entry file is located in the project folder based on the target configuration file. The operation is then performed based on the entry file.

[0011] Preferably, the method further includes:

[0012] When a project merge instruction is detected, the target projects to be merged are identified, and a merge folder is created in the source code file directory of the scaffolding system. The merge folder is used to store merge project resources, including merge project routes, merge project pages, entry scripts, and entry pages. The merge project pages include the project pages of each target project.

[0013] Add a route configuration file to the project resources of each target project, and add the route configuration files of each target project to the merged project route. The route configuration files are used to store all routes of the target projects.

[0014] Preferably, when a project merge instruction is detected, determining the target projects to be merged and creating a merge folder in the source code file directory of the scaffolding system includes:

[0015] When a project merge instruction is detected, identify the target projects to be merged;

[0016] When the scaffolding systems corresponding to the target projects are the same, a merge folder is created in the source code file directory of the scaffolding system;

[0017] When the scaffolding systems corresponding to each of the target projects are different, a new scaffolding system is created. In the new scaffolding system, a project folder is created for each target project. Each target project is copied into the project folder, and a merge folder is created in the source code file directory of the new scaffolding system.

[0018] Preferably, the method further includes:

[0019] Create a local component library, add common components and scripts of standardized reusable resources from various scaffolding systems to the local component library, and publish the library resources of the local component library based on the online package manager.

[0020] Preferably, the method further includes:

[0021] The resource information corresponding to each of the aforementioned library resources is labeled, and the resource information includes version information and update record information;

[0022] Whenever the local component library is updated, the version information corresponding to the current library resources is updated.

[0023] According to a second aspect, a scaffolding-based multi-project integrated front-end development device is provided, the device comprising:

[0024] The module is used to build a scaffolding system based on preset scaffolding tools, and to add a target configuration file for managing each project in the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0025] The search module is used to, when an execution instruction for any project is detected, search for the entry file in the project folder corresponding to the project based on the target configuration file, and perform the execution operation according to the entry file.

[0026] According to a third aspect, an electronic device is provided, including a processor and a memory;

[0027] The processor is connected to the memory;

[0028] The memory is used to store executable program code;

[0029] The processor runs a program corresponding to the executable program code stored in the memory to perform the steps of the method provided as in the first aspect or any possible implementation thereof.

[0030] According to a fourth aspect, a computer-readable storage medium is provided having a computer program stored thereon, the computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform the method provided as in the first aspect or any possible implementation thereof.

[0031] The solutions provided in the embodiments of this specification establish a new scaffolding system structure. Through folder management and a shared resource file mechanism, multiple projects can use a single scaffolding system simultaneously. This allows multiple projects to be centrally managed within a single scaffolding system, achieving a balance between project independence and resource sharing, thus improving development efficiency. Furthermore, by using a target configuration file to locate the entry file in the project folder, development operations for each project are executed separately, ensuring that each operation executed under this scaffolding system structure is precisely targeted at the specified project. Attached Figure Description

[0032] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0033] Figure 1 This is a flowchart illustrating a scaffolding-based multi-project integrated front-end development method provided as an embodiment of this specification.

[0034] Figure 2 This is a schematic diagram of the source code file directory structure of a scaffolding system provided in one embodiment of this specification.

[0035] Figure 3 This is a flowchart illustrating another scaffolding-based multi-project integrated front-end development method provided in one embodiment of this specification.

[0036] Figure 4 This is a schematic diagram of the source code file directory structure in a scaffolding system under a merged project scenario, as provided in one embodiment of this specification.

[0037] Figure 5 This is a flowchart illustrating another scaffolding-based multi-project integrated front-end development method provided in one embodiment of this specification.

[0038] Figure 6 This is a schematic diagram illustrating the working principle of a local component library provided in one embodiment of this specification.

[0039] Figure 7 This is a schematic diagram of a scaffold-based multi-project integrated front-end development device provided in one embodiment of this specification.

[0040] Figure 8 This is a schematic diagram of the structure of an electronic device provided in one embodiment of this specification. Detailed Implementation

[0041] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0042] In the following description, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The following description provides multiple embodiments of this application, which can be substituted or combined with each other. Therefore, this application can also be considered to include all possible combinations of the same and / or different embodiments described. Thus, if one embodiment includes features A, B, and C, and another embodiment includes features B and D, then this application should also be considered to include embodiments containing one or more other possible combinations of A, B, C, and D, even if such embodiments are not explicitly described in the following text.

[0043] The following description provides examples and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the described elements without departing from the scope of this application. Various processes or components may be appropriately omitted, substituted, or added to the examples. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined into other examples.

[0044] See Figure 1 , Figure 1 This is a flowchart illustrating a multi-project integrated front-end development method based on scaffolding, provided in an embodiment of this application. In this embodiment, the method includes:

[0045] S101. Build a scaffolding system based on preset scaffolding tools, and add a target configuration file for managing each project to the global configuration file of the scaffolding system.

[0046] The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0047] The entity executing this application may be a cloud server.

[0048] In the embodiments described in this specification, the cloud server will build a scaffolding system using pre-configured scaffolding tools. Compared to a conventional scaffolding structure, this scaffolding system will create a shared folder and a project folder in the source code file directory. The shared folder is used to centrally store standardized reusable resources, that is, common resources that are used by various projects, such as common components and scripts, for each project to call. Through this setting, each project can maintain independence from each other while maintaining consistency in the overall visual and functional architecture, and can coexist in one scaffolding system, which is convenient for management and development. Each project folder is a dedicated folder corresponding to each independent project, specifically used to store project resources related to that project. The specific content of project resources may vary depending on the project. Generally, project resources will include the complete set of configuration documents for that project, such as routes, pages, entry scripts, entry pages, etc. If a new project needs to be added later, a new project folder containing the project resources for that project will be added to the scaffolding system.

[0049] As an example, such as Figure 2 As shown in the diagram, `src` stands for `source`, a common directory name used to store the project's source code files. Within this source code directory, a shared folder and at least one project folder are set up. The number of project folders is the same as the number of projects currently existing in the scaffolding system, ensuring that each project has its own dedicated project folder. This enables parallel development of multiple projects with similar structures, layouts, and properties within a single scaffolding system, while also ensuring independent deployment capabilities for each project. It is applicable to various front-end frameworks such as Vue, React, and Angular. Taking a Vue project as an example, a complete Vue project's project folder contains project resources, i.e., a complete set of configuration documents, including `views` (for page storage), `router` (for routing, used for page path configuration), `main.js` (the entry script for accessing the project), and `App.vue` (the entry page for accessing the project).

[0050] In one possible implementation, the standardized reusable resources include shared common pages, common components, and common scripts, and the project resources include project routes, project pages, entry scripts, and entry pages.

[0051] In the embodiments of this specification, standardized reusable resources generally include common pages, common components, and common scripts for various projects to call. The project resources corresponding to each project should at least include the route and page corresponding to the project, as well as the entry script and entry page required to access and start the project.

[0052] S102. When an execution instruction for any project is detected, the entry file is searched in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

[0053] In the embodiments described in this specification, the system has a global configuration file. This application will introduce a target configuration file into the global configuration file to manage various projects. Whether developers want to run and debug a project or package and release it, an execution command for that project will be generated. After detecting the execution command, the cloud server will search for the entry file in the project folder of the project corresponding to the execution command in the scaffolding system through the target configuration file, and then perform the corresponding execution operation on the project through the entry file. The entry file includes the entry script and the entry page. Taking Vue as an example, its global configuration file is vue.config.js, and the Vue project will start according to vue.config.js. After introducing the target configuration file multi.conf in vue.config.js, when starting the project, the entry files such as App.vue and main.js of the project will be found through the multi.conf file, and the project will be started.

[0054] In one possible implementation, when an execution instruction for any project is detected, searching for an entry file in the project folder corresponding to the project based on the target configuration file, and performing the execution operation according to the entry file, includes:

[0055] When an execution instruction for any project is detected, the metadata file of the project is invoked, and the project name and the target configuration file corresponding to the project are determined based on the metadata file.

[0056] The project folder corresponding to the project is determined based on the project name, and the entry file is located in the project folder based on the target configuration file. The operation is then performed based on the entry file.

[0057] In the embodiments described in this specification, after detecting an execution command, the cloud server will call the metadata file of the project corresponding to the execution command to determine the project's metadata and configuration information, thereby determining the project name and its corresponding target configuration file. Next, based on this information, the corresponding project folder can be determined, and the entry file is queried within that project folder according to the target configuration file. Finally, the corresponding execution operation is performed based on the entry file.

[0058] See Figure 3 , Figure 3This is a flowchart illustrating another scaffolding-based multi-project integrated front-end development method provided in this application embodiment. In this application embodiment, the method includes:

[0059] S301. Build a scaffolding system based on preset scaffolding tools, and add a target configuration file for managing each project to the global configuration file of the scaffolding system.

[0060] The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0061] The entity executing this application may be a cloud server.

[0062] In the embodiments of this specification, step 301 can be referred to step 101, and will not be repeated here.

[0063] S302. When an execution instruction for any project is detected, the entry file is searched in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

[0064] In the embodiments of this specification, step 302 can be referred to step 102, and will not be repeated here.

[0065] S303. When a project merge instruction is detected, identify the target projects to be merged and create a merge folder in the source code file directory of the scaffolding system.

[0066] The merge folder is used to store merged project resources, which include merged project routes, merged project pages, entry scripts, and entry pages. The merged project pages include the project pages of each target project.

[0067] In the embodiments described in this specification, under certain circumstances, it is necessary to merge multiple projects into one project. In this case, the developers will send a project merge command to the cloud server. The cloud server will first determine the target projects that need to be merged based on the project merge command, and then create a merge folder in the scaffolding system. The structure of the merge folder is similar to the project folder corresponding to each project, and can be regarded as a folder for unified routing management. It is used to store the resources of the merged project. Subsequently, the integrated project can be launched directly through the entry script and entry page corresponding to the merge folder. The structural diagram of the merged scaffolding system can be shown as follows. Figure 4 As shown. The specific page information for the merged project page is derived from the page information of each individual project.

[0068] In one possible implementation, when a project merge instruction is detected, determining the target projects to be merged and creating a merge folder in the source code file directory of the scaffolding system includes:

[0069] When a project merge instruction is detected, identify the target projects to be merged;

[0070] When the scaffolding systems corresponding to the target projects are the same, a merge folder is created in the source code file directory of the scaffolding system;

[0071] When the scaffolding systems corresponding to each of the target projects are different, a new scaffolding system is created. In the new scaffolding system, a project folder is created for each target project. Each target project is copied into the project folder, and a merge folder is created in the source code file directory of the new scaffolding system.

[0072] In the embodiments described in this specification, considering that some projects may be long-term old projects that still use an old scaffolding structure where one scaffolding corresponds to only one project, it is necessary to first determine the scaffolding structure corresponding to each target project before integrating the target projects. If each target project uses the new scaffolding system structure built in this application, these target projects will correspond to one scaffolding system. In this case, a merge folder will be created directly in the source code file directory of the scaffolding system for subsequent merging operations. However, if each target project corresponds to a different scaffolding system, a new scaffolding system will be created first. This new scaffolding system is the structure proposed in this application, consisting of a shared folder and multiple project folders. Then, the cloud server will create a project folder for each target project in the new scaffolding system and copy the entire target project into that project folder to integrate all target projects into one scaffolding system. Only then will a merge folder be created in that scaffolding system for merging operations.

[0073] S304. Add a route configuration file to the project resources of each target project, and add the route configuration files of each target project to the merged project route.

[0074] The routing configuration file is used to store all routes for the target project.

[0075] In the embodiments described in this specification, after creating the merge folder, in order to form a large route covering all target projects within the merged project route of the merge folder, and thus enable the entire merged project to be launched directly through the merge folder, the cloud server also adds a route configuration file, allroutes.js, to the project resources of each target project. This route configuration file is used to store all routes for that project. Then, the route configuration files of each target project are imported into the merged project route added to the merge folder, making the merged project route a master route file that integrates the route information of each sub-project, enabling the merged project to be launched through the merge folder.

[0076] See Figure 5 , Figure 5 This is a flowchart illustrating another scaffolding-based multi-project integrated front-end development method provided in this application embodiment. In this application embodiment, the method includes:

[0077] S501. Build a scaffolding system based on preset scaffolding tools, and add a target configuration file for managing each project to the global configuration file of the scaffolding system.

[0078] The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0079] The entity executing this application may be a cloud server.

[0080] In the embodiments of this specification, step 501 can be referred to step 101, and will not be repeated here.

[0081] S502. When an execution instruction for any project is detected, the entry file is searched in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

[0082] In the embodiments of this specification, step 502 can be referred to step 102, and will not be repeated here.

[0083] S503. Create a local component library, add common components and scripts of standardized reusable resources from each scaffolding system to the local component library, and publish the library resources of the local component library based on the online package manager.

[0084] In the embodiments described in this specification, generally speaking, the interface design and layout style of different systems within the same enterprise will maintain a high degree of consistency and coherence to enhance the unity of brand image and user experience. This is because after building the new scaffolding system proposed in this application, projects are usually placed together, which facilitates centralized management and reuse of common components, styles, and logic code through shared folders. However, in special cases, due to the independence of business needs, some projects may need to build new scaffolding independently and use the scaffolding separately. This makes it impossible for these independent projects to directly share and reuse common resources. Therefore, in order to enable these independent projects to also use shared resources more conveniently, such as... Figure 6 As shown, a local component library is also created on the cloud server. Standardized reusable resources used by each project in each scaffolding system are added to the local component library, and the library resources of the local component library are uploaded to the online package manager for publication. In this way, independent projects can also directly download and use the common resources required by the project through the online package manager, realizing efficient resource sharing and reuse.

[0085] In one possible implementation, the method further includes:

[0086] The resource information corresponding to each of the aforementioned library resources is labeled, and the resource information includes version information and update record information;

[0087] Whenever the local component library is updated, the version information corresponding to the current library resources is updated.

[0088] In this embodiment, to ensure the effectiveness and timeliness of the public component library, the local component library will implement a version control strategy. Each time the library resources in the local component library are updated or modified, corresponding resource information will be provided. This resource information includes not only the updated version information but also update log information. The specific content of the update log information can be configured according to needs. For example, it could provide detailed documentation and sample code for the updated public components, helping developers quickly understand the component's purpose, usage, and expected behavior. Alternatively, it could explain the purpose of the update or the specific requirements of a project for which the adjustment was made, allowing developers to quickly understand whether the update is useful or disruptive to their project. With this setup, different versions of the library resources will exist in the online package manager, allowing developers to select and download the appropriate version according to their needs.

[0089] The following will be combined with the appendix Figure 7 This application provides a detailed description of the scaffolding-based multi-project integrated front-end development device provided in its embodiments. It should be noted that the appendix... Figure 7 The scaffold-based multi-project integrated front-end development apparatus shown is used to execute this application. Figure 7The methods shown in the embodiments are for illustrative purposes only, illustrating the parts relevant to the embodiments of this application. For specific technical details not disclosed, please refer to this application. Figure 1 The example shown.

[0090] Please see Figure 7 , Figure 7 This is a schematic diagram of a multi-project integrated front-end development device based on scaffolding, provided in an embodiment of this application. Figure 7 As shown, the device includes:

[0091] The module 701 is used to build a scaffolding system based on preset scaffolding tools, and to add a target configuration file for managing each project in the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0092] The lookup module 702 is used to, when an execution instruction for any project is detected, look up the entry file in the project folder corresponding to the project based on the target configuration file, and perform the execution operation according to the entry file.

[0093] In one possible implementation, the standardized reusable resources include shared common pages, common components, and common scripts, and the project resources include project routes, project pages, entry scripts, and entry pages.

[0094] In one possible implementation, the lookup module 702 is specifically used for:

[0095] When an execution instruction for any project is detected, the metadata file of the project is invoked, and the project name and the target configuration file corresponding to the project are determined based on the metadata file.

[0096] The project folder corresponding to the project is determined based on the project name, and the entry file is located in the project folder based on the target configuration file. The operation is then performed based on the entry file.

[0097] In one possible implementation, the device further includes:

[0098] The merge module is used to determine the target projects to be merged when a project merge instruction is detected, and to create a merge folder in the source code file directory of the scaffolding system. The merge folder is used to store merge project resources, including merge project routes, merge project pages, entry scripts and entry pages. The merge project pages include the project pages of each target project.

[0099] An add module is used to add a route configuration file to the project resources of each target project, and add the route configuration files of each target project to the merged project route. The route configuration files are used to store all routes of the target projects.

[0100] In one possible implementation, the merging module is specifically used for:

[0101] When a project merge instruction is detected, identify the target projects to be merged;

[0102] When the scaffolding systems corresponding to the target projects are the same, a merge folder is created in the source code file directory of the scaffolding system;

[0103] When the scaffolding systems corresponding to each of the target projects are different, a new scaffolding system is created. In the new scaffolding system, a project folder is created for each target project. Each target project is copied into the project folder, and a merge folder is created in the source code file directory of the new scaffolding system.

[0104] In one possible implementation, the device further includes:

[0105] A module is created to create a local component library, adding common components and scripts of standardized reusable resources from various scaffolding systems to the local component library, and publishing the library resources of the local component library based on the online package manager.

[0106] In one possible implementation, the device further includes:

[0107] The annotation module is used to annotate the resource information corresponding to each of the library resources, and the resource information includes version information and update record information.

[0108] The update module is used to update the version information of the current library resources whenever the local component library is updated.

[0109] Those skilled in the art will clearly understand that the technical solutions of the embodiments of this application can be implemented by means of software and / or hardware. In this specification, "unit" and "module" refer to software and / or hardware capable of independently completing or cooperating with other components to complete a specific function, wherein the hardware may be, for example, a Field-Programmable Gate Array (FPGA), an Integrated Circuit (IC), etc.

[0110] Each processing unit and / or module in the embodiments of this application can be implemented by an analog circuit that implements the functions described in the embodiments of this application, or by software that executes the functions described in the embodiments of this application.

[0111] See Figure 8 It shows a schematic diagram of the structure of an electronic device according to an embodiment of this application, which can be used to implement... Figure 1 The method in the illustrated embodiment. (As shown) Figure 8 As shown, the electronic device 800 may include: at least one processor 801, at least one network interface 804, a user interface 803, a memory 805, and at least one communication bus 802.

[0112] The communication bus 802 is used to enable communication between these components.

[0113] The user interface 803 may include a display screen and a camera. Optionally, the user interface 803 may also include a standard wired interface and a wireless interface.

[0114] The network interface 804 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0115] The processor 801 may include one or more processing cores. The processor 801 connects to various parts within the electronic device 800 using various interfaces and lines, and performs various functions and processes data by running or executing instructions, programs, code sets, or instruction sets stored in the memory 805, and by calling data stored in the memory 805. Optionally, the processor 801 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 801 may integrate one or a combination of several of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content required for display; and the modem handles wireless communication. It is understood that the modem may also be implemented as a separate chip without being integrated into the processor 801.

[0116] The memory 805 may include random access memory (RAM) or read-only memory. Optionally, the memory 805 may include a non-transitory computer-readable storage medium. The memory 805 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 805 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 805 may also be at least one storage device located remotely from the aforementioned processor 801. Figure 8 As shown, the memory 805, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and program instructions.

[0117] exist Figure 8 In the illustrated electronic device 800, the user interface 803 is mainly used to provide an input interface for the user and to obtain the user's input data; while the processor 801 can be used to call the scaffold-based multi-project integrated front-end development application stored in the memory 805, and specifically perform the following operations:

[0118] A scaffolding system is built based on preset scaffolding tools, and a target configuration file for managing each project is added to the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects.

[0119] When an execution instruction for any project is detected, the entry file is located in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

[0120] This application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the above-described method. The computer-readable storage medium may include, but is not limited to, any type of disk, including floppy disks, optical disks, DVDs, CD-ROMs, microdrives, as well as magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, DRAMs, VRAMs, flash memory devices, magnetic cards or optical cards, nanosystems (including molecular memory ICs), or any type of medium or device suitable for storing instructions and / or data.

[0121] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0122] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between devices or units may be electrical or other forms.

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

[0125] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0126] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0127] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, which may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0128] The foregoing description is merely an exemplary embodiment of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Those skilled in the art will readily conceive of embodiments of this disclosure upon considering the specification and practicing the disclosure herein. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described herein. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. A multi-project integrated front-end development method based on scaffolding, characterized in that, The method includes: A scaffolding system is built based on preset scaffolding tools, and a target configuration file for managing each project is added to the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects. When an execution instruction for any project is detected, the entry file is located in the project folder corresponding to the project based on the target configuration file, and the execution operation is performed according to the entry file.

2. The method according to claim 1, characterized in that, The standardized reusable resources include shared common pages, common components, and common scripts, while the project resources include project routes, project pages, entry scripts, and entry pages.

3. The method according to claim 1, characterized in that, When an execution instruction for any project is detected, the process of searching for an entry file in the project folder corresponding to the project based on the target configuration file, and performing the execution operation according to the entry file, includes: When an execution instruction for any project is detected, the metadata file of the project is invoked, and the project name and the target configuration file corresponding to the project are determined based on the metadata file. The project folder corresponding to the project is determined based on the project name, and the entry file is located in the project folder based on the target configuration file. The operation is then performed based on the entry file.

4. The method according to claim 1, characterized in that, The method further includes: When a project merge instruction is detected, the target projects to be merged are identified, and a merge folder is created in the source code file directory of the scaffolding system. The merge folder is used to store merge project resources, including merge project routes, merge project pages, entry scripts, and entry pages. The merge project pages include the project pages of each target project. Add a route configuration file to the project resources of each target project, and add the route configuration files of each target project to the merged project route. The route configuration files are used to store all routes of the target projects.

5. The method according to claim 4, characterized in that, When a project merge instruction is detected, the target projects to be merged are identified, and a merge folder is created in the source code file directory of the scaffolding system, including: When a project merge instruction is detected, identify the target projects to be merged; When the scaffolding systems corresponding to the target projects are the same, a merge folder is created in the source code file directory of the scaffolding system; When the scaffolding systems corresponding to each of the target projects are different, a new scaffolding system is created. In the new scaffolding system, a project folder is created for each target project. Each target project is copied into the project folder, and a merge folder is created in the source code file directory of the new scaffolding system.

6. The method according to claim 1, characterized in that, The method further includes: Create a local component library, add common components and scripts of standardized reusable resources from various scaffolding systems to the local component library, and publish the library resources of the local component library based on the online package manager.

7. The method according to claim 6, characterized in that, The method further includes: The resource information corresponding to each of the aforementioned library resources is labeled, and the resource information includes version information and update record information; Whenever the local component library is updated, the version information corresponding to the current library resources is updated.

8. A multi-project integrated front-end development device based on scaffolding, characterized in that, The device includes: The module is used to build a scaffolding system based on preset scaffolding tools, and to add a target configuration file for managing each project in the global configuration file of the scaffolding system. The source code file directory of the scaffolding system includes a shared folder and at least one project folder. The shared folder is used to store standardized reusable resources, and each project folder is used to store the project resources of an independent project. The number of project folders matches the number of independent projects. The search module is used to, when an execution instruction for any project is detected, search for the entry file in the project folder corresponding to the project based on the target configuration file, and perform the execution operation according to the entry file.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, the computer-readable storage medium storing instructions that, when executed on a computer or processor, cause the computer or processor to perform the steps of the method as claimed in any one of claims 1-7.

Images