jQuery UI Widgets Forums Angular Angular build giving warning for jqwidget class

This topic contains 2 replies, has 2 voices, and was last updated by  prashant.srivastava@intel.com 1 year, 11 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • Hi,

    I have a project in Angular 13, If I try to create a build (run a npm command ex:- npm run build:production) then It gives lots of warning related to css syntax error for jqwidget related css classes. Ex: “Warning: ▲ [WARNING] Expected identifier but found “*” [css-syntax-error]”

    And, If we look into the minified style (css) files of the build then it point to css class of jqwidget having * as an asterik. Below is the example picked from minified file (which build warning was specifying for my case)
    .jqx-notification-info,.jqx-info{color:#fff!important;text-shadow:0 -1px 0 rgba(0,0,0,.25)!important;background-color:#5bc0de!important;*background-color: #5bc0de !important

    Our application only supports Chrome and ITE Edge. Could you please suggest a fix for this ?
    Below is the configuration from our tsconfig.json file for target and lin


    admin
    Keymaster

    Hi prashant.srivastava@intel.com,

    You can safely remove it from the CSS file. This is added for browsers compatibility with old browsers.

    Best regards,
    Peter Stoev

    jQWidgets Team
    https://www.jqwidgets.com/

    Hi,

    Since jqwidget is a third party library and to my knowledge application should never be making changes to 3rd party libraries:

    Reason- Since, developer will only be bothered about package.json file and with the help of npm install command he/she will download the modules. And, If we make a change in 3rd libraries then on npm install command they will never get the version they are willing to use as it will be one which library such as jqwidget provides. Unless, developer make a change to file and host that package in his npm registry (place where packages are hosted).

    Not, all the packages are always hosted on npm registry.
    Isn’t there a way we can ignore these warning ?

    Regards,
    Prashant Srivastava

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.