For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

I hope we covered all possible cases 😄 maybe make sense to add more tests

The current implementation is somewhat saturated. Semicolons will be added in two situations:

1. If the code generated by each module's code generation starts with CHARS_REQUIRING_SEMICOLON, a semicolon will be added directly at the connection point.
2. When replacing finalName, if it starts with CHARS_REQUIRING_SEMICOLON, a semicolon must be added at the concatenation point. Although this semicolon is not always necessary, it is difficult to determine when finalName will appear at the beginning of the module, so it is added as a precaution.

In other cases, ASI should be evaluated in JavascriptParser. Here, we only assess scenarios where concatenating two modules requires ASI. CHARS_REQUIRING_SEMICOLON currently refers to situations where semicolons must be added at the beginning of a statement in JavaScript. Do you have any other suggestions for the cases that not covered? Thank you!

@fi3ework Yeah, I think all works fine, just more tests for each character https://github.com/webpack/webpack/pull/18709/files#diff-d34dd78b4ea6b37ac0551517562d61f39d0fc50699240a065ec8b13b37e2ed66R176

Got it, I'll update.