Henry-Hong opened a new pull request, #4787:
URL: https://github.com/apache/zeppelin/pull/4787

   ### What is this PR for?
   - Fix : https://issues.apache.org/jira/browse/ZEPPELIN-6052
   
   Background
   ---
   Currently, the Zeppelin web application uses Webpack for its build tools. 
Webpack provides valuable features like hot module replacement (HMR) through 
webpack-dev-server, which greatly enhances the development experience by 
automatically updating the UI in response to code changes.
   
   Unfortunately, hot module replacement is not functioning properly, impacting 
the developer experience, particularly on the frontend (zeppelin-web).
   
   Resolution
   ---
   
   To resolve this issue, I updated webpack-dev-server from version ^3.1.10 to 
^4.15.2. This update was selected as the latest version compatible with Webpack 
version 4.
   
   - Version Upgrade: Although I considered further upgrades, I chose the 
latest version compatible with Webpack version 4. I plan to migrate to Webpack 
version 5 incrementally.
   - Dependencies: The updated version 4.15.2 requires @webpack-cli/serve 
version ^1.2.0, which necessitated the installation of [email protected]. 
Consequently, I installed [email protected] too.
   - Configuration Changes: Due to BREAKING CHANGES introduced by the new 
version, modifications were required in the webpack.config.js to accommodate 
these updates.
   
   AS-IS
   ---
   ![화면 기록 2024-08-11 오후 3 14 
14](https://github.com/user-attachments/assets/b6d646e7-0019-4f03-a714-736a403e72ea)
   
   
   TO-BE
   ---
   ![화면 기록 2024-08-11 오후 1 57 
45](https://github.com/user-attachments/assets/a0446451-05a9-4983-b94a-f19b8e66208b)
   
   
   
   ### What type of PR is it?
   Bug Fix
   
   ### Todos
   * [x] Upgrade webpack-dev-server (3.1.10 -> 4.15.2)
   * [x] Install @webpack-cli/serve 
   * [x] Upgrade webpack-cli (3.3.12 -> 4.10.0)
   
   ### What is the Jira issue?
   * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/
   * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. 
[ZEPPELIN-533]
   
   ### How should this be tested?
   * Strongly recommended: add automated unit tests for any new or changed 
behavior
   * Outline any manual steps to test the PR here.
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the license files need to update?
   * Is there breaking changes for older versions?
   * Does this needs documentation?
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to