CN111142928A - Method and terminal for automatically constructing front-end project - Google Patents
Method and terminal for automatically constructing front-end project Download PDFInfo
- Publication number
- CN111142928A CN111142928A CN201911230979.0A CN201911230979A CN111142928A CN 111142928 A CN111142928 A CN 111142928A CN 201911230979 A CN201911230979 A CN 201911230979A CN 111142928 A CN111142928 A CN 111142928A
- Authority
- CN
- China
- Prior art keywords
- constructed
- end project
- project
- environment
- configuration file
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/76—Adapting program code to run in a different environment; Porting
Abstract
The invention discloses a method and a terminal for automatically constructing a front-end project, which are used for installing a package on which the front-end project to be constructed depends; acquiring an execution environment of a front-end project to be constructed; based on the dependent package, the front-end project to be constructed is packaged and the packaged front-end project is issued to the corresponding environment according to the execution environment, so that the automatic construction of the front-end project is realized, the front-end project only needs to be packaged once through the acquisition of the execution environment of the front-end project, different environments can be automatically distinguished according to the execution environment, the packaged front-end project is directly issued to the corresponding environment, the development process is simplified, and the development efficiency of the front-end project is improved.
Description
Technical Field
The invention relates to the technical field of networks, in particular to a method and a terminal for automatically constructing a front-end project.
Background
A standard front-end project usually passes through procedures such as babel compiling, webpack building and server starting, in the webpack building process, the webpack can build the project into a format which can be identified by a browser, then the project is issued to an online environment and displayed on the browser, in the process, an npm run build command is needed to pack the front-end project, when the packing is executed, a dist folder and an index. Generally, in which environment a front-end project is packaged, in which environment a packaged file is stored, and a front-end environment of the front-end project corresponds to a server address, therefore, when the front-end project needs to be uploaded to different environments, the project needs to be packaged once and then uploaded to the corresponding environment, and the server address and the corresponding configuration file need to be manually changed, which affects the development efficiency of the front-end project.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: the method and the terminal for automatically constructing the front-end project can simplify the development process of the front-end project and improve the development efficiency.
In order to solve the technical problems, the invention adopts the technical scheme that:
a method for automatically building a front-end project comprises the following steps:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a terminal for automatic construction of front-end projects, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
The invention has the beneficial effects that: the method comprises the steps of installing a package on which a front-end project to be constructed depends, obtaining an execution environment of the front-end project to be constructed, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding environment according to the execution environment, so that the automatic construction of the front-end project is realized. The front-end project needs to be constructed by means of third-party ready-made codes in the construction and packaging process, the front-end project can be conveniently constructed by using the shared codes provided by the package through installing the package on which the front-end project to be constructed depends, different environments can be automatically distinguished according to the execution environment only by packaging the front-end project once through acquiring the execution environment of the front-end project, the packaged front-end project is published to the corresponding environment, the development process is simplified, the development efficiency of the front-end project is improved, the method is different from the method that the traditional front-end project needs to undergo project packaging once when being uploaded to different environments, and the packaged file is manually stored to the corresponding environment.
Drawings
FIG. 1 is a flow chart illustrating steps of a method for automatically building a front-end project according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a terminal for automatically building a front-end project according to an embodiment of the present invention;
description of reference numerals:
1. a terminal for automatically constructing a front-end project; 2. a memory; 3. a processor.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
Referring to fig. 1, a method for automatically constructing a front-end project includes the steps of:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
As can be seen from the above description, the beneficial effects of the present invention are: the method comprises the steps of installing a package on which a front-end project to be constructed depends, obtaining an execution environment of the front-end project to be constructed, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding environment according to the execution environment, so that the automatic construction of the front-end project is realized. The front-end project needs to be constructed by means of third-party ready-made codes in the construction and packaging process, the front-end project can be conveniently constructed by using the shared codes provided by the package through installing the package on which the front-end project to be constructed depends, different environments can be automatically distinguished according to the execution environment only by packaging the front-end project once through acquiring the execution environment of the front-end project, the packaged front-end project is published to the corresponding environment, the development process is simplified, the development efficiency of the front-end project is improved, the method is different from the method that the traditional front-end project needs to undergo project packaging once when being uploaded to different environments, and the packaged file is manually stored to the corresponding environment.
Further, the step S2 further includes:
different environments correspond to different configuration file directories, and configuration files corresponding to the environments are arranged under the different configuration file directories;
the configuration files are a collection of settings and files required by the environment to be loaded.
According to the description, different configuration file directories are established for the operating environments of different front-end projects, so that the front-end projects can be connected to different servers according to the configuration files in the different configuration file directories when being packaged, the front-end projects are published in different environments, and the influence on the development efficiency of the front-end projects due to the fact that corresponding environments are built again is avoided.
Further, the step S2 includes:
setting an environment variable, and automatically acquiring the execution environment of the front-end project to be constructed according to the environment variable;
matching a corresponding configuration file directory according to the execution environment;
and acquiring a corresponding configuration file from the configuration file directory.
According to the above description, the current execution environment of the front-end project to be constructed is judged by setting the environment variables, the corresponding configuration file is matched with the execution environment, and the corresponding server address can be obtained based on the configuration file, so that the front-end project can automatically distinguish different server environments according to the obtained execution environment, and is connected to the specified server by using the corresponding configuration file, thereby avoiding that the server address and the configuration file need to be manually changed when the front-end project is packaged and uploaded to different environments every time, and simplifying the development process of the front-end project.
Further, the step S3 includes:
and operating a packaging command, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding CDN environment according to a configuration file corresponding to the execution environment of the front-end project to be constructed.
As can be seen from the above description, the packaging command is run, the project is delivered to the corresponding CDN environment according to the configuration file corresponding to the execution environment of the front-end project to be constructed, so that the project only needs to be packaged once, different server environments can be automatically distinguished according to the obtained execution environment of the front-end project, and the packaged file is sent to the corresponding environment, thereby improving the efficiency of front-end project development, unlike the conventional method in which the front-end project needs to undergo one-time project packaging when being uploaded to different environments, and then the packaged file is manually stored in the corresponding environment, the CDN serves as a content delivery network to deliver the packaged front-end project to the corresponding CDN environment, so that the static resources of the front-end project are cached in CDN nodes of a network operator that is close to the user, thereby increasing the speed of the user accessing the project, and saving the bandwidth consumption of the server, the load is reduced.
Further, the step S3 further includes:
before packaging the front-end item to be constructed, carrying out code specification check on the front-end item to be constructed once.
The code specification inspection is beneficial to unifying the code specification of a team, limiting the writing mode and annotation application of the code, and specifying the unified structure and mode of the code, so that the integrated logic of the code is favorably combed, the code is simpler and easier to understand, and when a front-end project needs to be modified and reconstructed, the code which is standard and tidy is more beneficial to a developer to modify the project.
Referring to fig. 2, a terminal for automatically building a front-end project includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor executes the computer program to implement the following steps:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
As can be seen from the above description, the beneficial effects of the present invention are: the method comprises the steps of installing a package on which a front-end project to be constructed depends, obtaining an execution environment of the front-end project to be constructed, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding environment according to the execution environment, so that the automatic construction of the front-end project is realized. The front-end project needs to be constructed by means of third-party ready-made codes in the construction and packaging process, the front-end project can be conveniently constructed by using the shared codes provided by the package through installing the package on which the front-end project to be constructed depends, different environments can be automatically distinguished according to the execution environment only by packaging the front-end project once through acquiring the execution environment of the front-end project, the packaged front-end project is published to the corresponding environment, the development process is simplified, the development efficiency of the front-end project is improved, the method is different from the method that the traditional front-end project needs to undergo project packaging once when being uploaded to different environments, and the packaged file is manually stored to the corresponding environment.
Further, the step S2 further includes:
different environments correspond to different configuration file directories, and configuration files corresponding to the environments are arranged under the different configuration file directories;
the configuration files are a collection of settings and files required by the environment to be loaded.
According to the description, different configuration file directories are established for the operating environments of different front-end projects, so that the front-end projects can be connected to different servers according to the configuration files in the different configuration file directories when being packaged, the front-end projects are published in different environments, and the influence on the development efficiency of the front-end projects due to the fact that corresponding environments are built again is avoided.
Further, the step S2 includes:
setting an environment variable, and automatically acquiring the execution environment of the front-end project to be constructed according to the environment variable;
matching a corresponding configuration file directory according to the execution environment;
and acquiring a corresponding configuration file from the configuration file directory.
According to the above description, the current execution environment of the front-end project to be constructed is judged by setting the environment variables, the corresponding configuration file is matched with the execution environment, and the corresponding server address can be obtained based on the configuration file, so that the front-end project can automatically distinguish different server environments according to the obtained execution environment, and is connected to the specified server by using the corresponding configuration file, thereby avoiding that the server address and the configuration file need to be manually changed when the front-end project is packaged and uploaded to different environments every time, and simplifying the development process of the front-end project.
Further, the step S3 includes:
and operating a packaging command, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding CDN environment according to a configuration file corresponding to the execution environment of the front-end project to be constructed.
As can be seen from the above description, the packaging command is run, the project is delivered to the corresponding CDN environment according to the configuration file corresponding to the execution environment of the front-end project to be constructed, so that the project only needs to be packaged once, different server environments can be automatically distinguished according to the obtained execution environment of the front-end project, and the packaged file is sent to the corresponding environment, thereby improving the efficiency of front-end project development, unlike the conventional method in which the front-end project needs to undergo one-time project packaging when being uploaded to different environments, and then the packaged file is manually stored in the corresponding environment, the CDN serves as a content delivery network to deliver the packaged front-end project to the corresponding CDN environment, so that the static resources of the front-end project are cached in CDN nodes of a network operator that is close to the user, thereby increasing the speed of the user accessing the project, and saving the bandwidth consumption of the server, the load is reduced.
Further, the step S3 further includes:
before packaging the front-end item to be constructed, carrying out code specification check on the front-end item to be constructed once.
The code specification inspection is beneficial to unifying the code specification of a team, limiting the writing mode and annotation application of the code, and specifying the unified structure and mode of the code, so that the integrated logic of the code is favorably combed, the code is simpler and easier to understand, and when a front-end project needs to be modified and reconstructed, the code which is standard and tidy is more beneficial to a developer to modify the project.
Example one
Referring to fig. 1, a method for automatically constructing a front-end project specifically includes the steps of:
s1, installing a package on which a front-end project to be constructed depends;
specifically, when a front-end project is developed, a Maven project management tool is used for realizing management and automatic construction of the front-end project, the configuration and construction dependency of the Maven project are written in a pom.xml file, the execution mode of project construction is configured in the pom.xml file, a specific implementation of a general plug-in is given through an < extensions > tag, the execution mode of an instruction "npm instance" for installing a package on which the front-end project to be constructed depends is defined in the pom.xml file, and the definition is as follows:
wherein id represents the operation identifier of the configuration information, goss represents the target of the plug-in to be executed, configuration represents the specific running configuration parameters of the execution, and when a command npminshall is input in a command line program, npm installs a package required by the project in the front-end project to be built and downloads all dependent packages according to the dependency relationship;
s2, acquiring an execution environment of a front-end project to be constructed;
specifically, the step S2 further includes:
different environments correspond to different configuration file directories, and configuration files corresponding to the environments are arranged under the different configuration file directories;
the configuration files are a collection of settings and files required by the environment to be loaded.
Specifically, when the server is configured, different configuration file directories are established for different front-end project environments, and corresponding configuration files are stored under the configuration file directories;
specifically, the step S2 includes:
setting an environment variable, and automatically acquiring the execution environment of the front-end project to be constructed according to the environment variable;
matching a corresponding configuration file directory according to the execution environment;
and acquiring a corresponding configuration file from the configuration file directory.
Specifically, an environment variable "npm config set sdp _ env $ { env }" is configured in the pom.xml file, and the configuration information is as follows:
wherein id represents the operation identifier of the configuration information, goss represents the target of the plug-in to be executed, configuration represents the specific running configuration parameters of the execution, a command npmconfigug set sdp _ env $ { env } is input in a command line program, the execution environment sdp _ env of the front-end item at the moment can be obtained, wherein $ { env } automatically receives the environment variables of the server end, and the configuration files preset by the corresponding server end are matched according to the execution environment of the front-end item at the moment;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
Specifically, the step S3 includes:
and operating a packaging command, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding CDN environment according to a configuration file corresponding to the execution environment of the front-end project to be constructed.
Specifically, an execution mode of the packed command "npm run dist" is defined in the pom.xml file, and is specifically defined as follows:
wherein id represents the operation identifier of the configuration information, gold represents the target of the plug-in to be executed, configuration represents the specific running configuration parameters of the execution, a command npm runlist is input in a command line program, a front-end item is packaged according to a shared code provided in an installed dependency package, a specified server is connected according to a configuration file corresponding to the acquired execution environment, and a disk file generated after packaging is issued to a CDN environment corresponding to the server.
Specifically, the step S3 further includes:
before packaging the front-end item to be constructed, carrying out code specification check on the front-end item to be constructed once.
Specifically, before packaging the front-end item to be constructed, a tool is used to perform a code specification check on the front-end item to be constructed.
Example two
Referring to fig. 2, a terminal with an automatically constructed front-end project, the terminal 1 includes a memory 2, a processor 3 and a computer program stored on the memory 2 and executable on the processor 3, and the processor 3 implements the steps in the first embodiment when executing the computer program.
To sum up, according to the method and the terminal for automatically constructing a front-end project provided by the present invention, by installing a package on which the front-end project to be constructed depends, the front-end project can conveniently construct the front-end project using a shared code provided by the package, setting an environment variable for automatically acquiring a current execution environment of the front-end project to be constructed, running a packaging command, performing a code specification check on the front-end project once, unifying code specifications of teams, defining an overall structure and a mode of a code, making a project code simpler and easier to understand, after the check is completed, packaging the front-end project, matching a corresponding configuration file according to the acquired current execution environment of the front-end project to be constructed, connecting to a designated server using the configuration file, issuing the packaged file to a CDN environment corresponding to the server, and by acquiring the current execution environment of the front-end project, the method has the advantages that the front-end project can be automatically distinguished according to the execution environment only by packing once, compared with the traditional method that the project is packed once when being released in different environments, and then is uploaded to the corresponding environment, the address of the server and the corresponding configuration file need to be manually changed, the development process of the front-end project is simplified, the development efficiency of the project is improved, meanwhile, the packed front-end project is released to the corresponding CDN environment, static resources of the front-end project are cached on CDN nodes of a network operator which is relatively close to a user, the speed of the user for accessing the project is increased, and the load of the server is reduced.
The above description is only an embodiment of the present invention, and not intended to limit the scope of the present invention, and all equivalent changes made by using the contents of the present specification and the drawings, or applied directly or indirectly to the related technical fields, are included in the scope of the present invention.
Claims (10)
1. A method for automatically constructing a front-end project is characterized by comprising the following steps:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
2. The method for automatically building a front-end project according to claim 1, wherein the step S2 further includes:
different environments correspond to different configuration file directories, and configuration files corresponding to the environments are arranged under the different configuration file directories;
the configuration files are a collection of settings and files required by the environment to be loaded.
3. The method for automatically building a front-end project according to claim 2, wherein the step S2 includes:
setting an environment variable, and automatically acquiring the execution environment of the front-end project to be constructed according to the environment variable;
matching a corresponding configuration file directory according to the execution environment;
and acquiring a corresponding configuration file from the configuration file directory.
4. The method for automatically building a front-end project according to claim 3, wherein the step S3 includes:
and operating a packaging command, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding CDN environment according to a configuration file corresponding to the execution environment of the front-end project to be constructed.
5. The method for automatically building a front-end project according to claim 1, wherein the step S3 further includes:
before packaging the front-end item to be constructed, carrying out code specification check on the front-end item to be constructed once.
6. A terminal for automatic construction of front-end projects, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the following steps when executing the computer program:
s1, installing a package on which a front-end project to be constructed depends;
s2, acquiring an execution environment of a front-end project to be constructed;
and S3, packaging the front-end item to be constructed based on the dependent package, and issuing the packaged front-end item to the corresponding environment according to the execution environment.
7. The terminal for automatic construction of front-end projects according to claim 6, wherein said step S2 further comprises:
different environments correspond to different configuration file directories, and configuration files corresponding to the environments are arranged under the different configuration file directories;
the configuration files are a collection of settings and files required by the environment to be loaded.
8. The terminal for automatic construction of front-end projects according to claim 7, wherein said step S2 includes:
setting an environment variable, and automatically acquiring the execution environment of the front-end project to be constructed according to the environment variable;
matching a corresponding configuration file directory according to the execution environment;
and acquiring a corresponding configuration file from the configuration file directory.
9. The terminal for automatic construction of front-end projects according to claim 8, wherein said step S3 includes:
and operating a packaging command, packaging the front-end project to be constructed based on the dependent package, and issuing the packaged front-end project to a corresponding CDN environment according to a configuration file corresponding to the execution environment of the front-end project to be constructed.
10. The terminal for automatic construction of front-end projects according to claim 6, wherein said step S3 further comprises:
before packaging the front-end item to be constructed, carrying out code specification check on the front-end item to be constructed once.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911230979.0A CN111142928A (en) | 2019-12-05 | 2019-12-05 | Method and terminal for automatically constructing front-end project |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911230979.0A CN111142928A (en) | 2019-12-05 | 2019-12-05 | Method and terminal for automatically constructing front-end project |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111142928A true CN111142928A (en) | 2020-05-12 |
Family
ID=70517536
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911230979.0A Pending CN111142928A (en) | 2019-12-05 | 2019-12-05 | Method and terminal for automatically constructing front-end project |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111142928A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113190268A (en) * | 2021-05-28 | 2021-07-30 | 宝宝巴士股份有限公司 | Packaging method of front-end source item |
| CN113282508A (en) * | 2021-06-11 | 2021-08-20 | 杭州安恒信息安全技术有限公司 | NPM-based tool class integration method, device, equipment and medium |
| CN114253630A (en) * | 2021-12-23 | 2022-03-29 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage by modifying Form change information based on Java section |
| CN116048533A (en) * | 2023-04-03 | 2023-05-02 | 浙江数新网络有限公司 | Implementation method and system for achieving dependency isolation in Flink task running |
| CN116149760A (en) * | 2023-04-21 | 2023-05-23 | 广州三晶电气股份有限公司 | Front-end project packaging method and device based on Vue frame |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105144092A (en) * | 2013-03-14 | 2015-12-09 | 微软技术许可有限责任公司 | Software release workflow management |
| CN105204916A (en) * | 2015-10-30 | 2015-12-30 | 北京奇虎科技有限公司 | Environment variable-based project process operation method and device |
| US20170003960A1 (en) * | 2015-01-30 | 2017-01-05 | Oracle International Corporation | System and method for automatic porting of software applications into a cloud computing environment |
| CN107704238A (en) * | 2017-11-28 | 2018-02-16 | 广州市千钧网络科技有限公司 | A kind of method and device packed to project |
| CN110147241A (en) * | 2019-04-16 | 2019-08-20 | 平安普惠企业管理有限公司 | Program configures update method, electronic device, computer equipment and storage medium |
-
2019
- 2019-12-05 CN CN201911230979.0A patent/CN111142928A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105144092A (en) * | 2013-03-14 | 2015-12-09 | 微软技术许可有限责任公司 | Software release workflow management |
| US20170003960A1 (en) * | 2015-01-30 | 2017-01-05 | Oracle International Corporation | System and method for automatic porting of software applications into a cloud computing environment |
| CN105204916A (en) * | 2015-10-30 | 2015-12-30 | 北京奇虎科技有限公司 | Environment variable-based project process operation method and device |
| CN107704238A (en) * | 2017-11-28 | 2018-02-16 | 广州市千钧网络科技有限公司 | A kind of method and device packed to project |
| CN110147241A (en) * | 2019-04-16 | 2019-08-20 | 平安普惠企业管理有限公司 | Program configures update method, electronic device, computer equipment and storage medium |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113190268A (en) * | 2021-05-28 | 2021-07-30 | 宝宝巴士股份有限公司 | Packaging method of front-end source item |
| CN113282508A (en) * | 2021-06-11 | 2021-08-20 | 杭州安恒信息安全技术有限公司 | NPM-based tool class integration method, device, equipment and medium |
| CN114253630A (en) * | 2021-12-23 | 2022-03-29 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage by modifying Form change information based on Java section |
| CN114253630B (en) * | 2021-12-23 | 2023-07-25 | 上海新炬网络信息技术股份有限公司 | Method for realizing log storage based on Java section modification Form change information |
| CN116048533A (en) * | 2023-04-03 | 2023-05-02 | 浙江数新网络有限公司 | Implementation method and system for achieving dependency isolation in Flink task running |
| CN116048533B (en) * | 2023-04-03 | 2023-07-25 | 浙江数新网络有限公司 | Implementation method and system for achieving dependency isolation in Flink task running |
| CN116149760A (en) * | 2023-04-21 | 2023-05-23 | 广州三晶电气股份有限公司 | Front-end project packaging method and device based on Vue frame |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111142928A (en) | Method and terminal for automatically constructing front-end project | |
| US20200184140A1 (en) | System and method for provisioning a mobile software application to a mobile device | |
| EP3377968B1 (en) | Dynamic update of an application in compilation and deployment | |
| US9161156B2 (en) | Tiles in a mobile application framework | |
| US8850416B1 (en) | System and method for creating target byte code | |
| US7707547B2 (en) | System and method for creating target byte code | |
| RU2601198C2 (en) | Runtime system | |
| US20190129734A1 (en) | Data collection workflow extension | |
| TWI556170B (en) | Projecting native application programming interfaces of an operating system into other programming languages (2) | |
| US10303449B2 (en) | Compiling non-native constants | |
| CN112835975B (en) | Method for deploying, updating and calling intelligent contracts in blockchain | |
| US11474796B1 (en) | Build system for distributed applications | |
| JP5811088B2 (en) | Data processing system and data processing method | |
| WO2011042228A1 (en) | Method and system to handle java class versioning | |
| US9244706B2 (en) | Command line shell command generation based on schema | |
| Waldén | Customizing BIOS/UEFI From OS Using EFI Variables | |
| Freeman et al. | Essential JavaScript Primer | |
| CN117591763A (en) | Method and system for managing sub-applications of main application based on micro front end |
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 |