RE: Liferay Angular Portlet - .jar size

2019-12-03T08:12:40Z

I really doubt that you need so many dependencies for runtime. For example, I don't think webpack is needed out of the scope of development, therefore it should be moved to devDependencies. I guess this may happen with others...

Once you decide which are dev and which runtime deps, you can also use exclusions (https://github.com/liferay/liferay-js-toolkit/wiki/.npmbundlerrc-file-reference#exclude) to get rid of unneeded files inside needed packages.

RE: Liferay Angular Portlet - .jar size

2019-12-02T16:45:35Z

I wouldn't declare 40mb as a problem.

You have the jar, open it with a zip tool and see what's in it. That way you'll know where the space is.

Often times you get all kinds of NPM dependencies to deal with. It wouldn't surprise me if you see a lot of stuff in there that maybe you do or don't need.

Liferay Angular Portlet - .jar size

2019-12-02T15:33:44Z

While developing an Angular portlet I noticed that the build takes 2-6 minutes and results in a ~40MB .jar.

The only changes I made to the original template were in package.json. There I updated the dependencies to match a current Angular CLI project.

{
&nbsp;&nbsp; &nbsp;"dependencies": {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/animations": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/cdk": "^8.2.3",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/common": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/compiler": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/core": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/forms": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/material": "^8.2.3",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/platform-browser": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/platform-browser-dynamic": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/router": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@ngx-translate/core": "^11.0.1",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"core-js": "^2.5.1",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"hammerjs": "^2.0.8",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"rxjs": "~6.4.0",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"tslib": "^1.10.0",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"zone.js": "~0.9.1",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"webpack": "4.41.2"
&nbsp;&nbsp; &nbsp;},
&nbsp;&nbsp; &nbsp;"devDependencies": {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular-devkit/build-angular": "~0.803.19",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/cli": "~8.3.19",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/compiler-cli": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@angular/language-service": "~8.2.14",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"@types/node": "~8.9.4",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"ts-node": "~7.0.0",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"tslint": "~5.15.0",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"typescript": "~3.5.3",
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"liferay-npm-bundler": "2.15.0"
&nbsp;&nbsp; &nbsp;},
&nbsp;&nbsp; &nbsp;"main": "lib/angular-loader.js",
&nbsp;&nbsp; &nbsp;"name": "liferay-angular8",
&nbsp;&nbsp; &nbsp;"scripts": {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;"build": "tsc &amp;&amp; liferay-npm-bundler"
&nbsp;&nbsp; &nbsp;},
&nbsp;&nbsp; &nbsp;"version": "1.0.0"
}

I already know that things got better after Liferay 7.0 (which I am using) but unfortunately I am stuck with it for now.

Are my build duration and size normal? Is there a way to optimize it?