Front-end development involves many moving parts. Sometimes it’s hard to tell what may be causing the issues you run into along the way. This can be particularly frustrating. These frequently asked questions and answers help you troubleshoot and correct problems arising during front-end development.
Here are the troubleshooting sections:
Click a question to view the answer.
A known bug with Angular causes absolute URLs for CSS files not to be recognized.
Due to the nature of portals, a relative URL is not an option either because the app can be placed on any page.
To fix this, you can either provide the CSS with a theme or themelet, or you can specify the path to the CSS file with the
com.liferay.portlet.header-portlet-css property in the portlet containing your Angular code.
By default CSS files are minified in the browser. This can cause issues in Internet Explorer. You can disable this behavior by including
minifier.enabled=false in your
There are a couple options you can use to disable reporting:
--no-trackingflag in your
package.json's build script to disable reporting:
.liferay-npm-bundler-no-trackingfile in your project's root folder, or any of its ancestors, to disable reporting.
This equates to answering
May liferay-npm-bundler anonymously report usage statistics to improve the tool over time?question.