This repository has been archived by the owner on Jun 2, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
Upgrade Angular Gateway to use Webpack 5 #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After upgrading to Angular 10, this is failing with the following error:
Any ideas @deepu105 @sendilkumarn? |
When I try to run the project with Maven, I get a different error:
|
Its been quite long since I worked with Angular so not much that I could think of, unfortunately :( |
That's cool @deepu105. Maybe @vishal423 can help? |
sorry, I haven't yet looked into the webpack v5. Above errors seems to be plugins incompatibility with the next webpack version and don't think we can do much over here. |
But do you really need webpack 5? Does it bring any drastic improvement?
…On Sat, 27 Jun 2020, 3:25 pm Vishal Mahajan, ***@***.***> wrote:
sorry, I haven't yet looked into the webpack v5. Above errors seems to be
plugins incompatibility with the next webpack version and don't think we
can do much over here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIOKF5V6KZC3AN7KFQSUB3RYXXOHANCNFSM4NPGPNQQ>
.
|
It's needed for module federation, which is what I want to try to use to implement micro frontends in JHipster.
https://webpack.js.org/concepts/module-federation/
… On Jun 27, 2020, at 11:48, Deepu K Sasidharan ***@***.***> wrote:
But do you really need webpack 5? Does it bring any drastic improvement?
On Sat, 27 Jun 2020, 3:25 pm Vishal Mahajan, ***@***.***>
wrote:
> sorry, I haven't yet looked into the webpack v5. Above errors seems to be
> plugins incompatibility with the next webpack version and don't think we
> can do much over here.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAIOKF5V6KZC3AN7KFQSUB3RYXXOHANCNFSM4NPGPNQQ>
> .
>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently fails with:
I believe this might be because of an incompatibility of @ngtools/webpack with Webpack 5. See https://stackoverflow.com/questions/61612636/mode-development-error-normalmodulefactory-beforeresolve-is-no-longer-a-water for more information.
Related: angular/angular-cli#17556