CN115617420A - Application program generation method, device, equipment and storage medium - Google Patents
Application program generation method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN115617420A CN115617420A CN202211381717.6A CN202211381717A CN115617420A CN 115617420 A CN115617420 A CN 115617420A CN 202211381717 A CN202211381717 A CN 202211381717A CN 115617420 A CN115617420 A CN 115617420A
- Authority
- CN
- China
- Prior art keywords
- module
- engineering
- file
- sub
- main
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 60
- 238000003860 storage Methods 0.000 title claims abstract description 21
- 238000004806 packaging method and process Methods 0.000 claims abstract description 23
- 230000006870 function Effects 0.000 claims description 73
- 238000012856 packing Methods 0.000 claims description 15
- 238000004590 computer program Methods 0.000 claims description 13
- 230000008676 import Effects 0.000 claims description 13
- 239000000126 substance Substances 0.000 claims 1
- 238000004891 communication Methods 0.000 description 11
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 8
- 238000007726 management method Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 8
- 238000011161 development Methods 0.000 description 5
- 238000009877 rendering Methods 0.000 description 5
- 239000000463 material Substances 0.000 description 4
- 238000005457 optimization Methods 0.000 description 4
- 230000010354 integration Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000004364 calculation method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000001953 sensory effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/44—Encoding
- G06F8/447—Target code generation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
- G06F8/24—Object-oriented
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The disclosure provides a method, a device, equipment and a storage medium for generating an application program, and relates to the technical field of computers, in particular to the technical field of software development and the technical field of micro front ends. The specific implementation scheme is as follows: acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file; adding a main engineering module and at least one sub-engineering module in a first configuration file; adding a view layer mounting operation code of a main engineering module in a first starting file; and packaging the added software engineering data to obtain the target application program.
Description
Technical Field
The present disclosure relates to the field of computer technology, and more particularly, to the field of software development and micro-front-end technology.
Background
In recent years, the application model of SaaS (Software-as-a-Service) as a Software Service has become mature. Many software service providers package developed software services into standard offerings for sale to users. However, many users have their own personalized customization requirements for software services, and the great customization requirements lead to the requirement that a software service provider needs to invest great manpower to perform customized development.
Disclosure of Invention
The disclosure provides a method, an apparatus, a device, a storage medium and a program product for generating an application program.
According to an aspect of the present disclosure, there is provided a method for generating an application program, including: acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file; adding a main engineering module and at least one sub-engineering module in the first configuration file; adding a view layer mounting operation code of the main engineering module in the first starting file; and packaging the added software engineering data to obtain a target application program.
According to another aspect of the present disclosure, there is provided an application generation apparatus including: the software engineering data acquisition module is used for acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file; the first lead-in module is used for adding a main engineering module and at least one sub-engineering module in the first configuration file; the second lead-in module is used for adding the view layer mounting operation codes of the main engineering module in the first starting file; and the first packing module is used for packing the added software engineering data to obtain a target application program.
Another aspect of the present disclosure provides an electronic device including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to cause the at least one processor to perform the method of the embodiments of the present disclosure.
According to another aspect of the disclosed embodiments, there is provided a non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method shown in the disclosed embodiments.
According to another aspect of the embodiments of the present disclosure, there is provided a computer program product comprising computer programs/instructions, characterized in that the computer programs/instructions, when executed by a processor, implement the steps of the method shown in the embodiments of the present disclosure.
It should be understood that the statements in this section are not intended to identify key or critical features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become apparent from the following description.
Drawings
The drawings are included to provide a better understanding of the present solution and are not to be construed as limiting the present disclosure. Wherein:
fig. 1 is a schematic view of an application scenario of an application generation method, an apparatus, an electronic device and a storage medium according to an embodiment of the present disclosure;
fig. 2 schematically shows a flow chart of a method of generation of an application according to an embodiment of the present disclosure;
FIG. 3 schematically shows a flow chart of a method of generating an application according to another embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart of a method of packaging master project data to yield a master project module, in accordance with an embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow diagram of a method of packaging sub-engineering data to obtain sub-engineering modules, according to an embodiment of the present disclosure;
fig. 6 schematically shows a schematic diagram of a generation method of an application according to an embodiment of the present disclosure;
FIG. 7 is a block diagram of a generation apparatus for an application program used to implement an embodiment of the present disclosure; and
FIG. 8 schematically shows a block diagram of an example electronic device that may be used to implement embodiments of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which various details of embodiments of the present disclosure are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the present disclosure. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
An application scenario of the application generation method and apparatus provided by the present disclosure will be described below with reference to fig. 1.
Fig. 1 is a schematic view of an application scenario of an application generation method, an application generation apparatus, an electronic device, and a storage medium according to an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of an application scenario in which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.
As shown in fig. 1, the application scenario 100 according to this embodiment may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have installed thereon various communication client applications, such as shopping-like applications, web browser applications, search-like applications, instant messaging tools, mailbox clients, social platform software, etc. (by way of example only).
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server providing various services, such as a background management server (for example only) providing support for websites or applications used by users browsing with the terminal devices 101, 102, 103. The backend management server may analyze and process the received data such as the user request, and feed back a processing result (for example, a web page, information, or data obtained or generated according to the user request) to the terminal device.
It should be noted that the method for generating the application provided by the embodiment of the present disclosure may be generally executed by the server 105. Accordingly, the generation apparatus of the application provided by the embodiment of the present disclosure may be generally disposed in the server 105. The generation method of the application provided by the embodiment of the present disclosure may also be executed by a server or a server cluster that is different from the server 105 and is capable of communicating with the terminal devices 101, 102, 103 and/or the server 105. Accordingly, the generating device of the application provided by the embodiment of the present disclosure may also be disposed in a server or a server cluster different from the server 105 and capable of communicating with the terminal devices 101, 102, 103 and/or the server 105.
It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for an implementation.
In the technical scheme of the disclosure, the collection, storage, use, processing, transmission, provision, disclosure, application and other processing of the personal information of the related user are all in accordance with the regulations of related laws and regulations, necessary confidentiality measures are taken, and the customs of the public order is not violated.
In the technical scheme of the disclosure, before the personal information of the user is acquired or collected, the authorization or the consent of the user is acquired.
The generation method of the application provided by the present disclosure will be described below with reference to fig. 2.
Fig. 2 schematically shows a flow chart of a generation method of an application according to an embodiment of the present disclosure.
As shown in fig. 2, the method 200 for generating the application program includes acquiring software engineering data in operation S210.
According to the embodiment of the disclosure, the software engineering data comprises a configuration file (config) and a start file (bootstrap), wherein the configuration file can comprise configuration information required when the software engineering data is packaged. The start-up file may be used to start the application. For convenience of description, the configuration file in the software engineering data is hereinafter referred to as a first configuration file, and the startup file in the software engineering data is hereinafter referred to as a first startup file.
It will be appreciated that the software engineering data may include other data in addition to the first configuration file and the first startup file, such as application page data, resource data, and so forth, which are not specifically limited by this disclosure.
Then, in operation S220, a main project module and at least one sub project module are added in the first configuration file.
According to the embodiment of the disclosure, a main engineering module and at least one sub-engineering module can be added in the first configuration file to introduce the main engineering module and the at least one sub-engineering module, so that the target application program can call the main engineering module and the at least one sub-engineering module. In addition, on the basis of adding the main engineering module and the at least one sub-engineering module in the first configuration file, data files corresponding to the main engineering module and the at least one sub-engineering module can be added to the software engineering data. The data file may include a configuration file, a startup file, application page data, resource data, and the like. Alternatively, the data files may be stored in other locations than the software engineering data, and the data files in the other locations may be obtained by introducing code during the running of the application program.
According to embodiments of the present disclosure, the main engineering module and the sub-engineering module may be packaged applications, respectively. The main engineering module may have an infrastructure function. The sub-engineering modules may have extended functionality beyond infrastructure functionality. The sub-engineering module can introduce the main engineering module to obtain a new sub-engineering module, and the new sub-engineering module has the infrastructure function of the main engineering module and other extension functions of the atomic engineering module.
The infrastructure functions may include business underlying functions that each sub-engineering module needs to refer to access the main engineering module, and may include, for example, a user information management function, a message center function, a material management function, and the like. The user information management function can be used for synchronizing information such as user states and operations related to user information between the sub-engineering module and the main engineering module. The message center function can be used for controlling the sub-engineering module and the main engineering module to call the same channel to receive messages, and can also have the functions of synchronously caching messages, synchronously sending roles and the like between the sub-engineering module and the main engineering module. The material management functions may be used to synchronize information such as material status and operations related to the material between the sub-project module and the main project module.
Other extended functions may include business functions that want to access the main engineering module in addition to infrastructure functions, which may include rich text editing functions, image editing functions, and the like, for example. Wherein the rich text editing function can be used for editing the rich text. The image editing function may be used to edit an image.
In operation S230, a view layer mount operation code of the main engineering module is added to the first start-up file.
According to the embodiment of the disclosure, the view layer mounting operation code of the main engineering module can be added in the first start-up file to introduce the view layer mounting operation code of the main engineering module, so that the view layer mounting operation code can be called when the first start-up file is executed.
According to the embodiment of the disclosure, the view layer mounting operation code of the main engineering module can be used for rendering the view layer of the main engineering module and adding the view layer to the corresponding page.
According to an embodiment of the present disclosure, operations between S220 and S230 may be performed in any order, which is not specifically limited by the present disclosure.
In operation S240, the added software engineering data is packaged to obtain the target application program.
According to the embodiment of the disclosure, the software engineering data can be packaged by using a packaging tool to obtain the target application program. Illustratively, in this embodiment, the packaging tool may comprise, for example, webpack.
In the related art, the process of customizing development software is cumbersome.
According to embodiments of the present disclosure, a main engineering module may have infrastructure functionality and a sub-engineering module may have customized extension functionality. Adding a main engineering module and at least one sub-engineering module in a first configuration file, and adding a view layer mounting operation code of the main engineering module in a first starting file. And packaging the software engineering data to obtain a target application program with an infrastructure function and an extension function, thereby simplifying the process of customizing the development software.
According to an embodiment of the present disclosure, a module federation plugin, hereinafter referred to as a first module federation plugin, may be added, for example, in a first configuration file. The module federal plug-in can be used for combining a plurality of independently constructed applications into one application. And then adding a main engineering module and at least one sub-engineering module in the first configuration file by utilizing the first module federal plug-in.
For example, a first module federal plug-in may be added in the first configuration file. And then, setting the introduction parameters of the federal plug-in of the first module according to the address of the main engineering module and the address of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file. The introduction parameter may be used to introduce other engineering modules other than the software engineering data into the software engineering data, that is, the other engineering modules are configured into a state that the target application program can call, that is, a calling state. For example, in this embodiment, the introduction parameter may be used to configure the main engineering module and the at least one sub-engineering module to be in a callable state. The address of the main engineering module indicates the storage address of the main engineering module, and the address of the sub engineering module indicates the storage address of the sub engineering module. Or, the introduction parameters of the federal plug-in of the first module can be set according to the acquisition code of the main engineering module and the acquisition code of the at least one sub engineering module, so that the main engineering module and the at least one sub engineering module can be added in the first configuration file. The acquisition code of the main engineering module can be used for acquiring the data file of the main engineering module, and the acquisition code of the sub engineering module can be used for acquiring the data file of the sub engineering module.
Illustratively, the Module Federation plug-in this embodiment may include, for example, the Module Federation plug-in webpack5. Based on this, for example, a plugins attribute may be set in the first configuration file, and an instance of Module Federation Plugin is imported to the plugins attribute, thereby adding the first Module Federal plug-in the first configuration file. In addition, the Module deployment Plugin may have a remote parameter into which the address of the main engineering Module and the address of the at least one sub-engineering Module may be passed or into which the acquisition code of the main engineering Module and the acquisition code of the at least one sub-engineering Module may be passed to introduce the main engineering Module and the sub-engineering Module.
If the applications are merged and packaged together to obtain an integrated application, the respective page optimization measures for each application may fail after integration.
According to the embodiment of the disclosure, by using the module federal plug-in, the main engineering module and the sub engineering module can be introduced into the application program, so that the application program can have the functions of the main engineering module and the sub engineering module, and original page optimization measures of the main engineering module and the sub engineering module can be reserved according to needs, wherein the optimization measures can comprise on-demand loading, route lazy loading, resource preloading and the like. In addition, the main engineering module and the sub-engineering module are introduced in a module federal plug-in mode, and good performance can be obtained without excessive optimization.
According to the embodiment of the disclosure, for example, a view layer mounting operation code of the main engineering module may be added at the tail of the first start-up file. By adding the view layer mounting operation code of the main engineering module at the tail part of the first starting file, the view layer mounting operation of the main engineering module can be executed at the final stage of starting. Because various code logics required by the mounting of the view layer at the final stage of the starting are loaded, the view layer can be normally mounted, and errors in the mounting process caused by the fact that the code logics required by the mounting of the view layer are not loaded can be avoided.
According to the embodiment of the disclosure, after the target application program is started, the entry files of the main engineering module and the entry files of the sub-engineering modules can be called according to the introduction parameters of the module federal plug-in, so that various code logics can be loaded, but the view layers are not mounted. And then, according to the tail introduction information of the first starting file, introducing a viewing layer mounting operation code exposed by the main engineering module, and starting the viewing layer mounting operation of the main engineering module, so that the viewing layer can be normally mounted, and errors in the mounting process caused by incomplete loading of code logic required by the viewing layer mounting are avoided.
Fig. 3 schematically shows a flow chart of a generation method of an application according to another embodiment of the present disclosure.
As shown in fig. 3, the method 300 for generating an application program may include packaging the main project data to obtain a main project module in operation S350.
In operation S360, the sub-project data is packed to obtain a sub-project module.
In operation S310, software engineering data is acquired.
Then, in operation S320, a main engineering module and at least one sub-engineering module are added in the first configuration file.
In operation S330, a view layer mount operation code of the main engineering module is added to the first start-up file.
In operation S340, the software engineering data is packaged to obtain the target application program.
According to an embodiment of the present disclosure, the master engineering data may include, for example, infrastructure function code, which may be used to provide infrastructure functionality. Based on this, the main engineering module may have an infrastructure function. In this regard, the sub-engineering data may be used, for example, to provide extended functionality beyond infrastructure functionality and the sub-engineering modules may have extended functionality beyond infrastructure functionality. In addition, the sub-engineering modules may be introduced into the main engineering module to obtain the infrastructure functionality of the main engineering module.
According to the embodiment of the present disclosure, for example, reference may be made to the above in operations S310 to S340, which are not described herein again.
According to an embodiment of the present disclosure, operations between S350 and S360 may be performed in any order, which is not specifically limited by the present disclosure.
According to the embodiment of the disclosure, the main engineering module and the sub-engineering module are obtained by respectively packaging the main engineering data and the sub-engineering data, so that developers can conveniently and freely combine the main engineering module and the sub-engineering module to obtain a target application program, and in addition, the labor cost and the time cost in the development process can be reduced. For example, the functional requirements of different users may be different, and based on this, for the functional requirements of each user, a developer may select a sub-engineering module matched with the functional requirements, and then generate a customized application meeting the functional requirements of the user according to the sub-engineering modules and the main engineering module, without separately developing an entire application for each user, thereby simplifying the process of customized software development.
The method for packaging the main engineering data to obtain the main engineering module provided by the present disclosure will be described below with reference to fig. 4.
FIG. 4 is a flow chart that schematically illustrates a method for packaging master project data into a master project module, in accordance with an embodiment of the present disclosure.
As shown in FIG. 4, the method 450 of packaging the main project data into a main project module includes obtaining the main project data in operation S451.
According to an embodiment of the present disclosure, the master project data may include a configuration file, a start-up file, an entry file, a core code module, and at least one infrastructure function code module. For convenience of description, the configuration file in the main project data is referred to as a second configuration file, the start file in the main project data is referred to as a second start file, and the entry file in the main project data is referred to as a first entry file. Wherein the second configuration file may include configuration information required when packaging the master project data. The second start-up file may be used to start the main engineering module. The first entry file may be the entry at the start of the main project module.
In operation S452, a second module federation plugin is added in a second configuration file.
According to an embodiment of the disclosure, a module federation plug-in, i.e., a second module federation plug-in, may be added in the second configuration file. For example, the module federation plug-in may be added to the first configuration file with reference to the above, and details are not described herein again.
In operation S453, the first import file is set to the exposed state in the second configuration file by the second module federation plugin.
According to the embodiment of the disclosure, by setting the first entry file to be in an exposed state, other applications except the main project module can access the first entry file.
At operation S454, at least one infrastructure function code is set to a shared state in a second configuration file by the second module federation plugin.
According to the embodiment of the disclosure, by setting the infrastructure function codes to the shared state, other applications besides the main engineering module can be made to call the infrastructure function codes.
According to an embodiment of the present disclosure, the infrastructure function code may be used to call the infrastructure function provided by the main engineering module, which may include, for example, an API (application program interface) that calls the infrastructure function provided by the main engineering module. The infrastructure function code may be in the form of a package (code module), such as an npm-package, for example.
According to an embodiment of the disclosure, a sharing parameter of the federal plug-in of the first module is set, for example, according to the identity of the at least one infrastructure function code, and the identity of the at least one infrastructure function code is set to be globally unique.
According to the embodiment of the disclosure, the infrastructure function provided by the main engineering module is split into packages and is subjected to API (application programming interface) to obtain the basic setting function code, and then the basic setting function code is exposed to other applications. The sub-function module can call various functions exposed by the main engineering module across the technical stack, so that the development process of an access party can be simplified.
According to the embodiment of the disclosure, the identification of the infrastructure function code is set to be globally unique, so that global dependencies are all in a single-instance form, and the problem of dependency conflict is avoided. In addition, in this embodiment, status information may be transmitted between the main engineering module and the sub-engineering module, and status information may also be transmitted between a plurality of sub-function modules, where the status information may include, for example, a login status. The state management among the modules can be well unified through a single-case mechanism.
In operation S455, the first entry file and the view layer mount operation code of the main engineering module are added to the second start-up file.
According to the embodiment of the disclosure, the view layer mounting operation code of the main engineering module can be used for rendering the view layer of the main engineering module and adding the view layer to the corresponding page.
According to the embodiment of the disclosure, the first entry file and the view layer mounting operation code of the main engineering module can be introduced by adding the first entry file and the view layer mounting operation code of the main engineering module in the second starting file, so that when the main engineering module is started, corresponding calling code logic can be loaded according to the first entry file. And then rendering the view layer according to the view layer mounting operation code, and adding the view layer into the page.
According to an embodiment of the present disclosure, operations S452 to S454 and S455 may be performed in any order, which is not particularly limited by the present disclosure.
In operation S456, the added main project data is packaged to obtain a main project module.
According to the embodiment of the disclosure, the main project data can be packaged by using a packaging tool to obtain the main project module. In this embodiment, the baling tool may comprise, for example, a webpack.
Illustratively, the Module Federation plug-in this embodiment may include, for example, the Module Federation plug-in webpack5. Based on this, for example, the expoes parameter of the Module Federation plug can be set in the second configuration file, and the storage path of the first entry file is passed into the expoes parameter to set the first entry file to be in the exposed state. For example, a shared parameter of the Module delivery plug may be set in the second configuration file, and a package identifier corresponding to the at least one infrastructure function code is transmitted to the shared parameter, so as to set the at least one infrastructure function code in the shared state. In addition, a singleton parameter may be set for each package, thereby constraining each package to be globally unique.
The method for packaging the sub-engineering data to obtain the sub-engineering module provided by the present disclosure will be described below with reference to fig. 5.
FIG. 5 schematically shows a flowchart of a method for packaging sub-engineering data to obtain sub-engineering modules according to an embodiment of the present disclosure.
As shown in fig. 5, the method 560 for packaging the sub-project data to obtain the main project module includes obtaining the sub-project data in operation S561.
According to an embodiment of the present disclosure, the sub-project data may include a configuration file, a start-up file, and an entry file. For convenience of description, the configuration file in the sub-project data is hereinafter referred to as a third configuration file, the startup file in the sub-project data is hereinafter referred to as a third startup file, and the entry file in the sub-project data is hereinafter referred to as a second entry file. Wherein the third configuration file may include configuration information required when packaging the sub-project data. The third start-up file may be used to start the promoter engineering module. The second entry file may be the entry at the time the sub-engineering module is started.
In operation S562, a third module federal plug-in is added in a third configuration file.
According to an embodiment of the present disclosure, a module federation plug-in, i.e., a third module federation plug-in, may be added in the third configuration file. For example, the module federation plug-in may be added to the first configuration file with reference to the above, and details are not described herein again.
In operation S563, the first entry file of the exposure status is added in a third configuration file through a third module federation plug-in.
According to the embodiment of the disclosure, the sub-engineering module can access the first entry file in the exposed state by adding the first entry file in the third configuration file.
In operation S564, an infrastructure function code of the shared state is added in a third configuration file through a third module federation plug-in.
According to the embodiment of the disclosure, by configuring the infrastructure function codes of the shared state in the third configuration file, the sub-engineering module can be enabled to call the infrastructure function codes.
In operation S565, the second entry file and the view layer mount operation code of the sub-engineering module are added to the third start-up file.
According to the embodiment of the disclosure, the view layer mounting operation codes of the sub-engineering modules can be used for rendering the view layers of the sub-engineering modules and adding the view layers to corresponding pages.
According to the embodiment of the disclosure, by introducing the second entry file and the view layer mounting operation code of the sub-engineering module into the third startup file, corresponding calling code logic can be loaded according to the second entry file when the sub-engineering module is started. And then rendering the view layer according to the view layer mounting operation code, and adding the view layer into the page.
According to an embodiment of the present disclosure, operations S562 to S564 and S565 may be performed in any order, which is not specifically limited by the present disclosure.
In operation S566, the added sub-project data is packaged to obtain a sub-project module.
According to the embodiment of the disclosure, the sub-engineering data can be packaged by using a packaging tool to obtain the sub-engineering module. Illustratively, in this embodiment, the packaging tool may comprise, for example, webpack.
The generation method of the application program described above is further described with reference to fig. 6 in conjunction with the specific embodiments. Those skilled in the art will appreciate that the following example embodiments are only for the understanding of the present disclosure, and the present disclosure is not limited thereto.
Fig. 6 schematically shows a schematic diagram of a generation method of an application according to an embodiment of the present disclosure.
In fig. 6 it is shown that at the main engineering module code level, the project code repository of the main engineering module can be converted into a multi-project form, for example mono-repo form. The core module may be an item ontology, hereinafter referred to as core, and splits the infrastructure function from the core to obtain at least one package, such as package1 and package2, where each infrastructure function corresponds to one package and is managed uniformly in mono-repo. Therefore, the uniformity of the dependent versions in the main engineering module can be guaranteed.
Exemplarily, in the present embodiment, at the build layer, the dependency of the master engineering module may be set to webpack5. The main engineering data can be edited by an editor, and then packaged by the webpack5 to obtain a main engineering module. The editor may include typescript, babel, esbuilt, and the like, for example.
For example, for a production environment, a Module Federal plug-in may be added in the webpack configuration file of the Main engineering Module using an editor. Wherein, the Module Federation plug has expeses and shared parameters. The core's entry file may then be exposed via the expose parameter. The entry file does not contain the operation of viewing layer mounting, and the operation of viewing layer mounting is responsible for a specific package. And uniformly providing the packages corresponding to the infrastructure functions to each access party through the shared parameters, and using singleton to restrict each package to be globally unique. In addition, the core dependency may also be constrained to be globally unique in the shared parameter. Core dependencies may include, for example, react, vue, etc.
For a development (depth) environment, an editor can be used for creating a bootstrap file for a main engineering module, and an introduction code of an entry file and a view layer mounting operation code are added in the bootstrap file. Then, the entry attribute of the webpack can be set as the bootstrap file, so that the project can be guaranteed to be started normally locally.
And then, packing the edited main engineering data by using the webpack5 to obtain a main engineering module. In addition, static resources in the master engineering data can be deployed to a CDN (content delivery network). Subsequently, the main engineering module can be provided to the user as a standard application.
According to an embodiment of the present disclosure, at a sub-engineering module code level, the sub-engineering modules may include, for example, guest1, guest2. At the build level, the dependencies of the sub-engineering modules may be set to webpack5. The sub-engineering data can be edited by an editor, and then packaged by the webpack5 to obtain a sub-engineering module. The editor may include typescript, babel, and esbuild, for example.
For example, the editor may be used to add Module Federation plug in the configuration file of the sub-engineering Module, and add the core of the main engineering Module by configuring the remote parameter of the Module Federation plug, for example, passing the remote parameter to the entry file address of the main function Module in the deployment CDN. And a bootstrap file can be created, and codes of the mounting view layer with the sub-engineering module are moved into the bootstrap file. And then asynchronously introducing the bootstrap file into the sub-engineering module entry file.
For a production environment, the editor may be utilized to import the bootstrap file header of the sub-engineering module into the core file exposed by the main engineering module via module-federation. The view layer mounting operation code exposed by the main engineering module can be introduced into the tail part of the bootstrap file of the sub-engineering module through the package.
For a development environment, the editor may be utilized to import the bootstrap file header of the sub-engineering module into the core file exposed by the main engineering module via module-federation. The visual layer mounting operation exposed by the main engineering module can be introduced and started through a package at the tail of the bootstrap file of the sub-engineering module. The sub-engineering module may also be launched locally when it is launched, if the main engineering module exposes other infrastructure functions, the sub-engineering module may be invoked. Therefore, the sub-engineering module can be directly and locally associated with the project of the main engineering module.
Next, the editor can be used to expose the entry files of the sub-engineering modules through the expose parameters of the Module Federation plug, introduce the package of each main engineering Module to be called through the shared parameter, and use singleton to constrain each package to be globally unique.
The sub-engineering modules may then be packaged to obtain sub-engineering modules. For example, gust 1 is packaged as a sub-project module 1 and gust 2 is packaged as a sub-project module 2.
At the integration layer, the main engineering Module and each sub-engineering Module can be added in the configuration file of the integrated project (i.e. the project integrating the main engineering Module and each sub-engineering Module) through the remote parameter of Module Federation plug-in. And introducing a code for starting the mounting operation of the view layer exposed by the main engineering module at the tail part of the bootstrap file of the integrated project through a package. The integration project can then be packaged and deployed, that is, all infrastructure functions and extended functions can be seen to be integrated in a micro front end manner. Subsequently, if no new sub-engineering module is accessed, the integrated project does not need to be redeployed, and the functional module can independently update the static resources to complete project updating.
For example, the main engineering module and the sub-engineering module 1 may be integrated to obtain a customized application 1. And integrating the main engineering module and the sub-engineering module 2 to obtain the customized application 2.
According to an embodiment of the present disclosure, a packaged application may be launched. After the packaged application is started, entry files of the main engineering Module and each sub-engineering Module can be called first according to the remote parameter of the Module Federation plug, code logic is loaded, and the view layer is not mounted. And then introducing information according to the package at the tail part of the bootstrap file, introducing a package corresponding to the view layer mounting operation exposed by the main engineering module, and starting the view layer mounting operation of the main engineering module according to the package.
The generation apparatus of the application provided by the present disclosure will be described below with reference to fig. 7.
Fig. 7 schematically shows a block diagram of a generation apparatus of an application according to an embodiment of the present disclosure.
As shown in fig. 7, the generating apparatus 700 of the application program includes an obtaining module 710, a first importing module 720, a second importing module 730, and a first packing module 740.
The first obtaining module 710 is configured to obtain software engineering data, where the software engineering data includes a first configuration file and a first startup file.
A first import module 720 for adding the main engineering module and the at least one sub-engineering module in the first configuration file.
The second import module 730 is configured to add the view layer mount operation code of the main engineering module in the first start-up file.
The first packing module 740 is configured to pack the added software engineering data to obtain the target application program.
According to an embodiment of the present disclosure, the first introduction module may include: the first adding submodule is used for adding a first module federal plug-in a first configuration file; and the first setting submodule is used for setting the introduction parameters of the federal plug-in of the first module according to the address of the main engineering module and the address of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module into the first configuration file.
According to an embodiment of the present disclosure, the first introduction module may include: the second adding submodule is used for adding the first module federal plug-in the first configuration file; and the second setting submodule is used for setting the introduction parameters of the federal plug-in of the first module according to the acquisition code of the main engineering module and the acquisition code of the at least one sub-engineering module so as to add the main engineering module and the at least one sub-engineering module in the first configuration file.
According to an embodiment of the present disclosure, the apparatus for generating an application program may further include: the second acquisition module is used for acquiring main project data, wherein the main project data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module; the third adding module is used for adding a second module federal plug-in a second configuration file; the exposure state setting module is used for setting the first entry file into an exposure state in a second configuration file through a second module federal plug-in; the shared state setting module is used for setting at least one infrastructure function code as a shared state in a second configuration file through a second module federal plug-in; the third lead-in module is used for adding the first entry file and the view layer mounting operation code of the main engineering module in the second starting file; and the second packing module is used for packing the added main project data to obtain a main project module.
According to an embodiment of the present disclosure, the shared state setting module may include: and the third setting submodule is used for setting the sharing parameter of the federated plugin of the first module according to the identifier of the at least one infrastructure function code, and setting the identifier of the at least one infrastructure function code to be globally unique, wherein the sharing parameter is used for configuring the at least one infrastructure function code into a sharing state.
According to an embodiment of the present disclosure, the apparatus for generating an application program may further include: the third acquisition module is used for acquiring sub-project data, wherein the sub-project data comprises a third configuration file, a third start file and a second entry file; the fourth adding module is used for adding a third module federal plug-in the third configuration file; the fourth introduction module is used for adding the first entry file in the exposed state in the third configuration file through the third module federation plugin; the fifth import module is used for adding the infrastructure function codes in the shared state in the third configuration file through the third module federal plug-in; the sixth import module is used for configuring the second entry file and the view layer mounting operation codes of the sub-engineering modules in the third starting file; and the third packing module is used for packing the added sub-engineering data to obtain a sub-engineering module.
According to an embodiment of the present disclosure, the second introduction module may include: and the sixth import submodule is used for adding the view layer mounting operation code of the main engineering module at the tail part of the first starting file.
The present disclosure also provides an electronic device, a readable storage medium, and a computer program product according to embodiments of the present disclosure.
Fig. 8 schematically illustrates a block diagram of an example electronic device 800 that may be used to implement embodiments of the present disclosure. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. Electronic devices may also represent various forms of mobile devices, such as personal digital processors, cellular telephones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be examples only, and are not meant to limit implementations of the disclosure described and/or claimed herein.
As shown in fig. 8, the apparatus 800 includes a computing unit 801 which can perform various appropriate actions and processes according to a computer program stored in a Read Only Memory (ROM) 802 or a computer program loaded from a storage unit 808 into a Random Access Memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the device 800 can also be stored. The calculation unit 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An input/output (I/O) interface 805 is also connected to bus 804.
A number of components in the device 800 are connected to the I/O interface 805, including: an input unit 806, such as a keyboard, a mouse, or the like; an output unit 807 such as various types of displays, speakers, and the like; a storage unit 808, such as a magnetic disk, optical disk, or the like; and a communication unit 809 such as a network card, modem, wireless communication transceiver, etc. The communication unit 809 allows the device 800 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.
Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), system on a chip (SOCs), complex Programmable Logic Devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.
Program code for implementing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
To provide for interaction with a user, the systems and techniques described here can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the computer. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.
The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), and the Internet.
The computer system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
The Server may be a cloud Server, also called a cloud computing Server or a cloud host, and is a host product in a cloud computing service system, so as to solve the defects of high management difficulty and weak service extensibility in a conventional physical host and VPS service ("Virtual Private Server", or "VPS" for short). The server may also be a server of a distributed system, or a server incorporating a blockchain.
It should be understood that various forms of the flows shown above, reordering, adding or deleting steps, may be used. For example, the steps described in the present disclosure may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired results of the technical solutions disclosed in the present disclosure can be achieved.
The above detailed description should not be construed as limiting the scope of the disclosure. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.
Claims (17)
1. A generation method of an application program comprises the following steps:
acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file;
adding a main engineering module and at least one sub-engineering module in the first configuration file;
adding a view layer mounting operation code of the main engineering module in the first starting file; and
and packaging the added software engineering data to obtain a target application program.
2. The method of claim 1, wherein said adding a main project module and at least one sub project module in said first configuration file comprises:
adding a first module federal plug-in the first configuration file; and
and setting the introduction parameters of the first module federal plug-in according to the address of the main engineering module and the address of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
3. The method of claim 1, wherein said adding a main engineering module and at least one sub-engineering module in the first configuration file comprises:
adding a first module federal plug-in the first configuration file; and
and setting the introduction parameters of the federal plug-in of the first module according to the acquisition code of the main engineering module and the acquisition code of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
4. The method of claim 2 or 3, further comprising:
acquiring main project data, wherein the main project data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module;
adding a second module federal plug-in the second configuration file;
setting, by the second module federation plug-in, the first entry file in the second configuration file to an exposed state;
setting, by the second module federation plug-in, the at least one infrastructure function code to a shared state in the second configuration file;
adding the first entry file and a view layer mounting operation code of the main engineering module in the second starting file; and
and packaging the added main project data to obtain the main project module.
5. The method of claim 4, wherein said setting, by the second module federation plug-in, the at least one infrastructure function code in the second configuration file to a shared state comprises:
and setting a sharing parameter of the first module federal plug-in according to the identification of at least one infrastructure function code, and setting the identification of the at least one infrastructure function code to be globally unique, wherein the sharing parameter is used for configuring the at least one infrastructure function code to be in a sharing state.
6. The method of claim 1, further comprising:
acquiring sub-project data, wherein the sub-project data comprises a third configuration file, a third starting file and a second entry file;
adding a third module federal plug-in the third configuration file;
adding a first entry file of an exposed state in the third configuration file through the third module federal plug-in;
adding, by the third module federation plugin, infrastructure function code in a shared state in the third configuration file;
adding the second entry file and a view layer mounting operation code of the sub-engineering module in the third starting file; and
and packaging the added sub-engineering data to obtain the sub-engineering module.
7. The method according to claim 1, wherein the adding of the view layer mount operation code of the main engineering module in the first startup file comprises:
and adding a view layer mounting operation code of the main engineering module at the tail part of the first starting file.
8. An apparatus for generating an application program, comprising:
the software engineering data acquisition module is used for acquiring software engineering data, wherein the software engineering data comprises a first configuration file and a first starting file;
the first lead-in module is used for adding a main engineering module and at least one sub-engineering module in the first configuration file;
the second introduction module is used for adding the view layer mounting operation codes of the main engineering module in the first starting file; and
and the first packing module is used for packing the added software engineering data to obtain the target application program.
9. The apparatus of claim 8, wherein the first introduction module comprises:
the first adding submodule is used for adding a first module federal plug-in the first configuration file; and
and the first setting submodule is used for setting the introduction parameters of the first module federal plug-in according to the address of the main engineering module and the address of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
10. The apparatus of claim 8, wherein the first introduction module comprises:
the second adding submodule is used for adding a first module federal plug-in the first configuration file; and
and the second setting submodule is used for setting the introduction parameters of the federal plug-in of the first module according to the acquisition code of the main engineering module and the acquisition code of the at least one sub engineering module so as to add the main engineering module and the at least one sub engineering module in the first configuration file.
11. The apparatus of claim 9 or 10, further comprising:
the second acquisition module is used for acquiring main project data, wherein the main project data comprises a second configuration file, a second starting file, a first entry file, a core code module and at least one infrastructure function code module;
the third adding module is used for adding a second module federal plug-in the second configuration file;
an exposure state setting module, configured to set the first entry file to an exposure state in the second configuration file through the second module federation plug-in;
a shared state setting module, configured to set the at least one infrastructure function code to a shared state in the second configuration file through the second module federation plug-in;
a third import module, configured to add the first entry file and the view layer mount operation code of the main engineering module to the second start file;
and the second packing module is used for packing the added main project data to obtain the main project module.
12. The apparatus of claim 11, wherein the shared state setting module comprises:
and the third setting submodule is used for setting the sharing parameter of the first module federal plug-in according to the identification of at least one infrastructure function code, and setting the identification of the at least one infrastructure function code as global uniqueness, wherein the sharing parameter is used for configuring the at least one infrastructure function code into a sharing state.
13. The apparatus of claim 11, further comprising:
the third acquisition module is used for acquiring sub-project data, wherein the sub-project data comprises a third configuration file, a third start file and a second entry file;
a fourth adding module, configured to add a third module federal plug-in to the third configuration file;
a fourth import module, configured to add, through the third module federal plug-in, a first entry file in an exposed state in the third configuration file;
a fifth import module, configured to add, through the third module federal plug-in, an infrastructure function code in a shared state in the third configuration file;
a sixth import module, configured to configure the second entry file and the view layer mount operation code of the sub-engineering module in the third start-up file; and
and the third packing module is used for packing the added sub-engineering data to obtain the sub-engineering module.
14. The apparatus of claim 8, wherein the second introduction module comprises:
and the sixth import submodule is used for adding the view layer mounting operation code of the main engineering module at the tail part of the first starting file.
15. An electronic device, comprising:
at least one processor; and
a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-7.
16. A non-transitory computer readable storage medium having stored thereon computer instructions for causing the computer to perform the method of any one of claims 1-7.
17. A computer program product comprising computer program/instructions, characterized in that the computer program/instructions, when executed by a processor, implement the steps of the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211381717.6A CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211381717.6A CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115617420A true CN115617420A (en) | 2023-01-17 |
| CN115617420B CN115617420B (en) | 2024-03-01 |
Family
ID=84878985
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211381717.6A Active CN115617420B (en) | 2022-11-03 | 2022-11-03 | Application program generation method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115617420B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116069325A (en) * | 2023-01-28 | 2023-05-05 | 深圳市明源云采购科技有限公司 | Front-end project construction method, device, equipment and computer readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN110442327A (en) * | 2018-05-03 | 2019-11-12 | 阿里巴巴集团控股有限公司 | A kind of application builds method, apparatus, server |
| CN113157345A (en) * | 2021-04-30 | 2021-07-23 | 中国工商银行股份有限公司 | Automatic starting method and device for front-end engineering |
| CN113220367A (en) * | 2021-05-12 | 2021-08-06 | 北京百度网讯科技有限公司 | Applet running method and device, electronic equipment and storage medium |
-
2022
- 2022-11-03 CN CN202211381717.6A patent/CN115617420B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107291458A (en) * | 2017-06-06 | 2017-10-24 | 北京知道创宇信息技术有限公司 | A kind of plug-in unit construction method, system and the server of Web applications |
| CN110442327A (en) * | 2018-05-03 | 2019-11-12 | 阿里巴巴集团控股有限公司 | A kind of application builds method, apparatus, server |
| CN113157345A (en) * | 2021-04-30 | 2021-07-23 | 中国工商银行股份有限公司 | Automatic starting method and device for front-end engineering |
| CN113220367A (en) * | 2021-05-12 | 2021-08-06 | 北京百度网讯科技有限公司 | Applet running method and device, electronic equipment and storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116069325A (en) * | 2023-01-28 | 2023-05-05 | 深圳市明源云采购科技有限公司 | Front-end project construction method, device, equipment and computer readable storage medium |
| CN116069325B (en) * | 2023-01-28 | 2023-08-04 | 深圳市明源云采购科技有限公司 | Front-end project construction method, device, equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115617420B (en) | 2024-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110795195B (en) | Webpage rendering method and device, electronic equipment and storage medium | |
| CN113010827B (en) | Page rendering method and device, electronic equipment and storage medium | |
| CN111338623B (en) | Method, device, medium and electronic equipment for developing user interface | |
| CN111090423B (en) | Webhook framework system and method for realizing active calling and event triggering | |
| CN113808231B (en) | Information processing method and device, image rendering method and device, and electronic device | |
| CN110007936B (en) | Data processing method and device | |
| CN112612467A (en) | Method and device for processing micro front-end architecture based on qiankun | |
| CN113821352A (en) | Remote service calling method and device | |
| CN115617420B (en) | Application program generation method, device, equipment and storage medium | |
| CN111381899A (en) | Method and apparatus for developing target system | |
| CN110851211A (en) | Method, apparatus, electronic device, and medium for displaying application information | |
| CN112214250A (en) | Application program assembly loading method and device | |
| CN110807162A (en) | Method and device for loading occupation bitmap | |
| CN110795328A (en) | Interface testing method and device | |
| CN110795135A (en) | Method and device for realizing injection-resolution configuration | |
| CN113760264A (en) | Method and device for multiplexing components among multiple applications | |
| CN112596854A (en) | Method and device for continuously integrating running of assembly line | |
| CN111414154A (en) | Method and device for front-end development, electronic equipment and storage medium | |
| WO2023169193A1 (en) | Method and device for generating smart contract | |
| CN111382953A (en) | Dynamic process generation method and device | |
| CN113656041A (en) | Data processing method, device, equipment and storage medium | |
| CN113094561A (en) | Webpage generation method, webpage generation device, electronic equipment and storage medium | |
| CN113778566A (en) | Native application calling method and device, electronic equipment and computer readable medium | |
| CN113760487A (en) | Service processing method and device | |
| CN114157917B (en) | Video editing method and device and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |