CN114546436A - Micro front-end service updating method and device, electronic equipment and storage medium - Google Patents

Abstract

The present disclosure relates to a method and an apparatus for updating a micro front-end service, an electronic device and a storage medium, including: responding to a development instruction of the sub-service, acquiring a target file, wherein the target file is a target file of the latest version of a main service to which the sub-service belongs, and the sub-service and the main service are services based on a micro front-end framework; acquiring configuration information of the sub-service, starting a webpage server of the sub-service according to the configuration information, and writing the configuration information into a target file to obtain an updated target file; and reading the updated target file, and starting the webpage server of the updated main service, wherein the updated main service comprises the sub-items. Therefore, after a development instruction is received, the target file of the main service can be automatically configured, a developer only needs to concentrate on development configuration and business development of the sub-service in the micro front-end application, and the micro front-end service can be automatically updated, so that the efficiency of local integrated development of the micro front-end is improved.

Description

A micro-front-end service update method, device, electronic device and storage medium

technical field

The present disclosure relates to the field of application testing, and in particular, to a micro-front-end service update method, device, electronic device and storage medium.

Background technique

Micro-front-end applications are composed of multiple front-end applications, where each front-end application is independent of each other and does not interfere with each other. For users, a micro-front-end application is a complete application, but the multiple front-end applications included in the micro-front-end application are independent of each other in the development and testing process, and then combined in some way to obtain the micro-front-end application.

That is to say, in the process of development and testing, the micro-front-end application is used as a main service, which includes sub-services corresponding to multiple front-end applications. At present, the mainstream micro-front-end framework in the front-end development industry can realize the technology stack between sub-services. Unrelated, supports independent development, independent deployment of sub-services, and runtime isolation of sub-services.

However, during the development process, the developer needs to download and start the main service server and the sub-service server locally. If the remote main service code repository is updated, the developer cannot perceive it in real time, and it needs to be updated manually. Moreover, the developer also needs to To start the micro-frontend development mode, manually modify the development configuration items of the main service and sub-services. Therefore, the overall process is cumbersome, the development cost of micro-frontend access is high, the update of micro-frontend services is not convenient, and the development experience and efficiency are very low.

SUMMARY OF THE INVENTION

The present disclosure provides a micro-front-end service update method, device, electronic device and storage medium, so as to at least solve the cumbersome overall process in related technologies, the high cost of micro-front-end access and development, the inconvenience of updating the micro-front-end service, and the high development experience and efficiency. low problem. The technical solution of the present disclosure is as follows:

According to a first aspect of the embodiments of the present disclosure, a method for updating a micro-frontend service is provided, applied to an electronic device, and the method includes:

In response to the development instruction for the sub-service, obtain a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs, and both the sub-service and the main service are based on the micro-frontend framework. Serve;

Obtain the configuration information of the sub-service, start the web server of the sub-service according to the configuration information, and write the configuration information in the target file to obtain the updated target file;

Read the updated target file, start the web server of the updated main service, and the updated main service includes the sub-service.

Optionally, obtaining the target file in response to the development instruction for the sub-service includes:

In response to the development instruction to the sub-service, obtain the latest version information of the target file of the main service from the preset database;

Determine whether the latest version information is consistent with the locally stored version information of the target file of the main service;

If inconsistent, obtain the target file of the main service from the preset database, and update the target file of the main service stored locally.

Optionally, if the latest version information is consistent with the version information of the target file of the main service stored locally, the method further includes:

Get the target file of the main service stored locally.

Optionally, after the acquiring the target file, the method further includes:

Obtain the installation file of the dependent software package from the target file, download and install the dependent software package according to the installation file, and the dependent software package is an external target file required by the main service;

The described reading of the updated target file, and starting the web server of the updated main service, include:

Read the updated target file, call the dependent software package, and start the updated web server of the main service.

Optionally, writing the configuration information into the target file to obtain an updated target file, including:

generating a simulation file of the sub-service according to the configuration information;

query whether the target file includes the simulation file corresponding to the sub-service;

If included, then the simulation file in the described target file is replaced by the simulation file that is generated, obtains described updated target file;

If not included, the simulation file is added to the target file to obtain the updated target file.

Optionally, reading the updated target file and starting the updated web server of the main service, including:

Read the simulation file of at least one sub-service included in the updated target file, and obtain the configuration information of the at least one sub-service;

Start the web server of the updated main service, and register the at least one sub-service in the updated main service according to the configuration information of the at least one sub-service.

Optionally, the obtaining configuration information of the sub-service includes:

In response to the development instruction, a scaffolding tool is used to create a template file of the sub-service;

In response to the editing instruction for the template file, the configuration information of the sub-service is acquired.

According to a second aspect of the embodiments of the present disclosure, a micro-front-end service updating apparatus is provided, applied to electronic equipment, and the apparatus includes:

an obtaining unit, configured to execute a development instruction in response to the sub-service, and obtain a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs, the sub-service and the main service All are services based on the micro front-end framework;

an update unit, configured to obtain the configuration information of the sub-service, start the web server of the sub-service according to the configuration information, and write the configuration information into the target file to obtain the updated target file ;

A startup unit, configured to read the updated target file, and start the web server of the updated main service, where the updated main service includes the sub-service.

Optionally, the obtaining unit is configured to execute:

In response to the development instruction to the sub-service, obtain the latest version information of the target file of the main service from the preset database;

Determine whether the latest version information is consistent with the locally stored version information of the target file of the main service;

If inconsistent, obtain the target file of the main service from the preset database, and update the target file of the main service stored locally.

Optionally, the obtaining unit is configured to execute:

If the latest version information is consistent with the version information of the target file of the main service stored locally, the target file of the main service stored locally is acquired.

Optionally, the obtaining unit is configured to execute:

Obtain the installation file of the dependent software package from the target file, download and install the dependent software package according to the installation file, and the dependent software package is an external file required by the main service;

The startup unit, configured to execute:

Read the updated target file, call the dependent software package, and start the updated web server of the main service.

Optionally, the updating unit is configured to execute:

generating a simulation file of the sub-service according to the configuration information;

query whether the target file includes the simulation file corresponding to the sub-service;

If included, then the simulation file in the described target file is replaced by the simulation file that is generated, obtains described updated target file;

If not included, the simulation file is added to the target file to obtain the updated target file.

Optionally, the updating unit is configured to execute:

Read the simulation file of at least one sub-service included in the updated target file, and obtain the configuration information of the at least one sub-service;

Start the web server of the updated main service, and register the at least one sub-service in the updated main service according to the configuration information of the at least one sub-service.

Optionally, the updating unit is configured to execute:

In response to the development instruction, a scaffolding tool is used to create a template file of the sub-service;

In response to the editing instruction for the template file, the configuration information of the sub-service is acquired.

According to a third aspect of the embodiments of the present disclosure, a micro-frontend service updating electronic device is provided, including:

processor;

memory for storing instructions executable by the processor;

Wherein, the processor is configured to execute the instructions to implement the micro-frontend service update method described in the first item above.

According to a fourth aspect of the embodiments of the present disclosure, a computer-readable storage medium is provided, and when instructions in the computer-readable storage medium are executed by a processor of a micro-frontend service updating electronic device, the micro-frontend service updates the electronic device The micro-frontend service update method described in any one of the above can be executed.

According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer program product, including computer programs/instructions, when the computer programs/instructions are executed by a processor, the micro-frontend service updating method described in the first item above is implemented.

The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects:

In response to the development instruction for the sub-service, the electronic device acquires a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs; acquires the configuration information of the sub-service, starts the web server of the sub-service according to the configuration information, and Write the configuration information into the target file to obtain the updated target file; read the updated target file, start the web server of the updated main service, and the updated main service includes sub-items.

That is to say, after receiving the development instruction, the target file of the main service can be automatically configured, so that the developer only needs to focus on the development configuration and business development of the sub-service in the micro-frontend application, and does not need to care about the main service corresponding to the sub-service. How to pull, update, and configure the code of the service, the micro-frontend service can be automatically updated, thereby improving the efficiency of the local integrated development of the micro-frontend.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate embodiments consistent with the present disclosure, and together with the description, serve to explain the principles of the present disclosure and do not unduly limit the present disclosure.

Fig. 1 is a flow chart of a method for updating a micro-frontend service according to an exemplary embodiment.

FIG. 2 is a flowchart of S101 in FIG. 1 according to an exemplary embodiment.

FIG. 3 is a flowchart of S102 in FIG. 1 according to an exemplary embodiment.

Fig. 4 is a block diagram of an apparatus for updating a micro-frontend service according to an exemplary embodiment.

Fig. 5 is a block diagram of an electronic device for updating a micro-frontend service according to an exemplary embodiment.

Fig. 6 is a block diagram of an apparatus for updating a micro-frontend service according to an exemplary embodiment.

Detailed ways

In order to make those skilled in the art better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

It should be noted that the terms "first", "second" and the like in the description and claims of the present disclosure and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein can be practiced in sequences other than those illustrated or described herein. The implementations described in the illustrative examples below are not intended to represent all implementations consistent with this disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as recited in the appended claims.

Fig. 1 is a flowchart of a method for updating a micro-frontend service according to an exemplary embodiment. As shown in Fig. 1 , the method for updating a micro-frontend service is applied to an electronic device, and specifically includes the following steps.

In step S101, in response to the development instruction for the sub-service, a target file is obtained, the target file is a file for running the latest version of the main service to which the sub-service belongs, and both the sub-service and the main service are services based on the micro-frontend framework.

In the present disclosure, an electronic device can run a micro-front-end application, and a micro-front-end application is formed by aggregating multiple front-end applications, wherein each front-end application is independent from each other and does not interfere with each other. As a main service, a front-end application includes sub-services corresponding to multiple front-end applications. Developers can develop and test sub-services corresponding to individual front-end applications.

In this step, the target file is a file used to run the latest version of the main service to which the sub-service belongs, which may be a code file or a compiled instruction file, which is not specifically limited. In one implementation, the target file can be obtained directly from the preset database, and in another implementation, a backup of the target file of the main service is stored locally. In this case, the target file of the local storage main service can be compared with The version of the target file in the preset database.

Specifically, as shown in FIG. 2, it is a schematic flowchart of S101 in an implementation manner, which includes the following steps:

S1011: Acquire the latest version information of the target file of the main service from the preset database in response to the development instruction for the sub-service.

The preset database may be a git database, and the target file of the main service is stored in the git database. The target file of the main service is usually the package.json file, and the version information of the target file is usually the version field in the package.json, which can be the version number composed of numbers, or the date of the version update, etc., which are not limited in detail.

S1012: Determine whether the latest version information is consistent with the version information of the target file of the main service stored locally, if not, execute S1013; if they are consistent, execute S1014.

S1013: Acquire the target file of the main service from the preset database, and update the target file of the main service stored locally. In this way, by judging the consistency of the latest version information of the target file, it can be ensured that the obtained target file is the latest version, and at the same time, the locally stored target file can be updated in a timely and active manner.

In an implementation manner, updating the target file of the locally stored main service may be to modify the locally stored version according to the difference between the locally stored version and the version in the preset database, or it may also be in the latest version. If the information is inconsistent with the version information of the target file of the main service stored locally, delete the target file of the main service stored locally, and then download and back it up again from the preset database.

S1014: Obtain the target file of the main service stored locally as the target file. In this way, the number of times and the amount of data to be pulled from the preset database can be reduced, and the occupation of system resources can be reduced.

In this way, by locally storing the backup of the target file of the main service, the number of times of obtaining the target file from the preset database can be reduced, thereby reducing the data transmission load and improving the efficiency. Moreover, the latest code of the main service of the micro-frontend can be automatically pulled, reducing the The operation process required by developers to improve development efficiency.

In this disclosure, a micro-front-end development framework is used between the sub-service and the main service, such as the qiankun (Qiankun) framework or the single-spa (single page web application, single-page application) framework, etc. Install the micro-front-end development scaffolding tool locally, and then receive the development instructions. The development instructions can carry specific command functions and transfer parameters in the micro-front-end development scaffolding tool. For example, the developer can enter the following content in turn to send Development command: "ksc serve—port 3000—force".

In an implementation manner, after obtaining the target file, the installation file of the dependent software package may be obtained from the target file, and the dependent software package may be downloaded and installed according to the installation file. Among them, the installation file can be a script file or an ordinary source code file, which is not limited in detail. For example, the installation file can be npm install, which depends on the external files required by the software package as the main service, usually in the package.json file dependencies and devDependencies field, external files can be code files or compiled instruction files, etc.

In this way, since the target file is the latest version of the file used to run the main service, the dependent package is also the latest external file required by the main service. After installing the dependent package, the updated target file can be read by Call the dependent software package to start the web server of the updated micro-frontend main service. The web server of the main service is the web server used to provide the main service. In other words, automatic updates to the main service can be achieved, improving the efficiency of local integrated development of micro-frontends.

In step S102, the configuration information of the sub-service is acquired, the web server of the sub-service is started according to the configuration information, and the configuration information is written into the target file to obtain the updated target file.

In this step, the configuration information of the sub-service is determined according to the configuration of the developer, wherein the configuration information of the sub-service can be read from the configuration file .sub-app.js, which includes the domain name (host) and port of the sub-service. One or more pieces of information, such as port number (port), service name (project name), and service homepage url (uniform resource locator, uniform resource locator) address.

The configuration information is written into the target file, which can be specifically written into the simulation file included in the target file. The simulation file is the mock file, and the configuration file of the sub-service can be located in the root directory of the sub-service in the target file. In the testing process, for some objects that are not easy to construct or obtain, a corresponding virtual mock file is created, and the mock file is tested, so as to realize the testing of these objects that are not easy to construct or obtain.

Specifically, acquiring the configuration information of the sub-service may include: first, in response to the development instruction, using a scaffolding tool to create a template file of the sub-service; then, in response to an editing instruction for the template file, acquiring the configuration information of the sub-service.

The scaffolding tool is a tool that can automatically create a service template file. The template file can define information such as the infrastructure of the service, the specifications and conventions for providing services, etc., that is, the configuration of the sub-service based on the template file created by the scaffolding tool. , which can reduce the repetitive development work in the same main service, and further realize the automation of local integrated development and debugging of micro-frontends.

As shown in FIG. 3, it is a schematic flowchart of S102 in an implementation manner, which includes the following steps:

S1021: Generate a simulation file of the sub-service according to the configuration information.

The simulation file may include information such as the service identifier (project key), service name, and service homepage URL address of the corresponding sub-service, and the service identifier is used to query whether the target file includes the simulation file corresponding to the sub-service. The key value projectKey to query.

S1022: Query whether the target file includes the simulation file corresponding to the sub-service; if included, execute S1023; if not, execute S1024.

S1023: Replace the simulation file in the target file with the generated simulation file to obtain an updated target file.

S1024: Add the simulation file to the target file to obtain the updated target file.

That is to say, if the sub-service simulation file with the same name already exists in the target file, the sub-service simulation file with the same name is directly overwritten. If the sub-service simulation file with the same name does not exist in the target file, the simulation file is added to the target file. Start the web server running the sub service according to the latest simulation file of the sub service. The web server of the sub service is the web server used to provide the sub service, so as to avoid the situation that the web server of the sub service provides an old version of the sub service after it is started.

In step S103, the updated target file is read, the web server of the updated main service is started, and the updated main service includes sub-services.

In an implementation mode, the updated target file is read, and the web server of the updated main service is started, which can specifically include:

First, read the simulation file of at least one sub-service included in the updated target file to obtain the configuration information of at least one sub-service; then, start the web server of the updated main service, and according to the configuration information of at least one sub-service , register at least one sub-service in the updated main service.

Wherein, the configuration information of the sub-service may include any one or more items such as the service identifier of the sub-service, the service name, and the url address of the service homepage. In this way, by reading the simulation file in the target file, the electronic device can start the web server of the updated main service without completely constructing or acquiring the data of the main service, and at the same time, the new sub-service can be automatically registered in the main service , which also realizes the automatic update of sub-services in the main service, reducing the manual operation of developers.

After updating the target file, you can read the updated target file and start the web server of the updated main service. Since the updated target file includes the configuration information of the sub-service, after reading the updated target file, the configuration information of the sub-service in the simulation file can be parsed, and then the list of registered sub-services can be added to the micro-frontend framework, so as to realize Automatically start the web server of the micro-frontend sub-service, and further develop and test the sub-service.

As can be seen from the above, the technical solutions provided by the embodiments of the present disclosure can automatically configure the target file of the main service after receiving the development instruction, so that the developer only needs to focus on the development configuration of the sub-service in the micro-frontend application and For business development, there is no need to care about how to pull, update, and configure the code of the main service corresponding to the sub-service. The micro-frontend service can be automatically updated, thereby improving the efficiency of the local integrated development of the micro-frontend.

Fig. 4 is a block diagram of a micro-front-end service updating apparatus shown according to an exemplary embodiment, the apparatus is applied to electronic equipment, and the apparatus includes:

The obtaining unit 201 is configured to execute a development instruction in response to a sub-service, and obtain a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs, the sub-service and the main service. The services are all services based on the micro front-end framework;

The updating unit 202 is configured to execute the acquisition of configuration information of the sub-service, start the web server of the sub-service according to the configuration information, and write the configuration information into the target file to obtain the updated target document;

The starting unit 203 is configured to read the updated target file and start the web server of the updated main service, where the updated main service includes the sub-service.

In an implementation manner, the obtaining unit 201 is configured to execute:

In response to the development instruction to the sub-service, obtain the latest version information of the target file of the main service from the preset database;

Determine whether the latest version information is consistent with the locally stored version information of the target file of the main service;

If inconsistent, the target file of the main service is obtained from the preset database as the target file, and the locally stored target file of the main service is updated.

In an implementation manner, the obtaining unit 201 is configured to execute:

If the latest version information is consistent with the version information of the target file of the main service stored locally, the target file of the main service stored locally is acquired.

In an implementation manner, the obtaining unit 201 is configured to execute:

Obtain the installation file of the dependent software package from the target file, download and install the dependent software package according to the installation file, and the dependent software package is an external file required by the main service;

The startup unit 203 is configured to execute:

Read the updated target file, call the dependent software package, and start the updated web server of the main service.

In an implementation manner, the updating unit 202 is configured to execute:

generating a simulation file of the sub-service according to the configuration information;

query whether the target file includes the simulation file corresponding to the sub-service;

If included, then replace the simulated file in the described target file with the generated simulated file to obtain the updated target file;

If not included, the simulation file is added to the target file to obtain an updated target file.

In an implementation manner, the updating unit 202 is configured to execute:

Read the simulation file of at least one sub-service included in the updated target file, and obtain the configuration information of the at least one sub-service;

Start the web server of the updated main service, and register the at least one sub-service in the updated main service according to the configuration information of the at least one sub-service.

In an implementation manner, the updating unit 202 is configured to execute:

In response to the development instruction, a scaffolding tool is used to create a template file of the sub-service;

In response to the editing instruction for the template file, the configuration information of the sub-service is acquired.

As can be seen from the above, the technical solutions provided by the embodiments of the present disclosure can automatically configure the target file of the main service after receiving the development instruction, so that the developer only needs to focus on the development configuration of the sub-service in the micro-frontend application and For business development, there is no need to care about how to pull, update, and configure the code of the main service corresponding to the sub-service. The micro-frontend service can be automatically updated, thereby improving the efficiency of the local integrated development of the micro-frontend.

Regarding the apparatus in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be described in detail here.

Fig. 5 is a block diagram of an electronic device for updating a micro-frontend service according to an exemplary embodiment.

In an exemplary embodiment, there is also provided a computer readable storage medium, such as a memory including instructions, executable by a processor of an electronic device to perform the above method. Alternatively, the computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program product which, when run on a computer, causes the computer to implement the above-described method for updating a micro-frontend service.

As can be seen from the above, the technical solutions provided by the embodiments of the present disclosure can automatically configure the target file of the main service after receiving the development instruction, so that the developer only needs to focus on the development configuration of the sub-service in the micro-frontend application and For business development, there is no need to care about how to pull, update, and configure the code of the main service corresponding to the sub-service, thereby improving the efficiency of local integrated development of micro-frontends.

FIG. 6 is a block diagram of an apparatus 800 for updating a micro-frontend service according to an exemplary embodiment.

For example, apparatus 800 may be a mobile phone, computer, digital broadcast electronics, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, or the like.

6, the apparatus 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, And the communication component 816.

The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to perform all or some of the steps of the methods described above. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

Memory 804 is configured to store various types of data to support operation at device 800 . Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

Power supply assembly 807 provides power to the various components of device 800 . Power supply components 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 800 .

Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

Audio component 810 is configured to output and/or input audio signals. For example, audio component 810 includes a microphone (MIC) that is configured to receive external audio signals when device 800 is in operating modes, such as calling mode, recording mode, and voice recognition mode. The received audio signal may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: home button, volume buttons, start button, and lock button.

Sensor assembly 814 includes one or more sensors for providing status assessment of various aspects of device 800 . For example, the sensor assembly 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect a change in the position of the device 800 or a component of the device 800 , the presence or absence of user contact with the device 800 , the orientation or acceleration/deceleration of the device 800 and the temperature change of the device 800 . Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

Communication component 816 is configured to facilitate wired or wireless communication between apparatus 800 and other devices. Device 800 may access a wireless network based on a communication standard, such as WiFi, a carrier network (eg, 2G, 3G, 4G, or 5G), or a combination thereof. In one exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable A gate array (FPGA), controller, microcontroller, microprocessor or other electronic component implementation for performing the methods of the first and second aspects.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium including instructions, such as memory 804 including instructions, executable by the processor 820 of the apparatus 800 to perform the method described above. Alternatively, for example, the storage medium may be a non-transitory computer-readable storage medium, for example, the non-transitory non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), CD-ROMs, magnetic tapes, floppy disks, and optical data storage devices, etc.

In an exemplary embodiment, there is also provided a computer program product comprising instructions which, when executed on a computer, cause the computer to execute the micro-frontend service updating method described in the first embodiment above.

As can be seen from the above, the technical solutions provided by the embodiments of the present disclosure can automatically configure the target file of the main service after receiving the development instruction, so that the developer only needs to focus on the development configuration of the sub-service in the micro-frontend application and For business development, there is no need to care about how to pull, update, and configure the code of the main service corresponding to the sub-service. The micro-frontend service can be automatically updated, thereby improving the efficiency of the local integrated development of the micro-frontend.

Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or techniques in the technical field not disclosed by the present disclosure . The specification and examples are to be regarded as exemplary only, with the true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise structures described above and illustrated in the accompanying drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. a micro front-end service update method, is characterized in that, is applied to electronic equipment, and described method comprises: In response to the development instruction for the sub-service, obtain a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs, and both the sub-service and the main service are based on the micro-frontend framework. Serve; Obtain the configuration information of the sub-service, start the web server of the sub-service according to the configuration information, and write the configuration information into the target file to obtain an updated target file; The updated target file is read, and the web server of the updated main service is started, and the updated main service includes the sub-service. 2. The micro-front-end service update method according to claim 1, wherein, in response to the development instruction to the sub-service, obtaining the target file, comprising: In response to the development instruction for the sub-service, obtain the latest version information of the target file of the main service from the preset database; Determine whether the latest version information is consistent with the locally stored version information of the target file of the main service; If not, the target file of the main service is acquired from the preset database, and the target file of the main service stored locally is updated. 3. The micro-front-end service update method according to claim 2, wherein if the latest version information is consistent with the version information of the target file of the main service stored locally, the method further comprises: Get the target file of the main service stored locally. 4. The micro-frontend service update method according to claim 1, wherein after the acquiring the target file, the method further comprises: Obtain an installation file of a dependent software package from the target file, download and install the dependent software package according to the installation file, and the dependent software package is an external file required by the main service; The described reading of the updated target file, and starting the web server of the updated main service, include: Read the updated target file, call the dependent software package, and start the updated web server of the main service. 5. The micro-front-end service updating method according to claim 1, wherein the writing the configuration information into the target file to obtain an updated target file, comprising: generating a simulation file of the sub-service according to the configuration information; query whether the target file includes the simulation file corresponding to the sub-service; If included, replace the simulation file in the target file with the generated simulation file to obtain the updated target file; If not included, the simulation file is added to the target file to obtain the updated target file. 6. The micro-front-end service updating method according to claim 5, wherein the reading the updated target file and starting the web server of the updated main service, comprising: Read the simulation file of at least one sub-service included in the updated target file, and obtain the configuration information of the at least one sub-service; The web server of the updated main service is started, and the at least one sub-service is registered in the updated main service according to the configuration information of the at least one sub-service. 7. The micro-frontend service update method according to claim 1, wherein the acquiring the configuration information of the sub-service comprises: In response to the development instruction, a scaffolding tool is used to create a template file of the sub-service; In response to the editing instruction for the template file, the configuration information of the sub-service is acquired. 8. A micro-front-end service update device, characterized in that, applied to electronic equipment, the device comprising: an obtaining unit, configured to execute a development instruction in response to the sub-service, and obtain a target file, where the target file is a file used to run the latest version of the main service to which the sub-service belongs, the sub-service and the main service All are services based on the micro front-end framework; an update unit, configured to obtain the configuration information of the sub-service, start the web server of the sub-service according to the configuration information, and write the configuration information into the target file to obtain the updated target file ; A startup unit, configured to read the updated target file, and start a web server of the updated main service, where the updated main service includes the sub-service. 9. An electronic device, characterized in that, comprising: processor; memory for storing instructions executable by the processor; Wherein, the processor is configured to execute the instructions to implement the micro-frontend service update method according to any one of claims 1 to 7. 10. A computer-readable storage medium, characterized in that, when the instructions in the computer-readable storage medium are executed by the processor of the micro-front-end service updating electronic device, the micro-front-end service updating electronic device can be executed as claimed in the claims The micro-frontend service update method described in any one of 1 to 7.

Images