You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the library's less files are depending on javascriptEnabled option in less-loader config, unfortunately due to security issues this feature was deprecated long ago...
I have seen that Angular still uses this flag in his default Webpack config for less but going forward I guess it is a good idea to remove as I am not sure how long it will keep being supported (it is no longer works with higher less-loader versions...).
Currently it is blocking me from creating custom themes, which really pull me back from using this awesome library, I will be glad if you could fix that soon...
The text was updated successfully, but these errors were encountered:
This problem has been on for 4 years. It's about a high time to remove javascriptEnabled feature from sass styles:
▲ [WARNING] Deprecated inline execution of JavaScript has been enabled ("javascriptEnabled") [plugin angular-less]
node_modules/ng-zorro-antd/style/color/bezierEasing.less:110:0:
110 │ .bezierEasingMixin();
╵ ^
JavaScript found within less stylesheets may be executed at build time. [https://lesscss.org/usage/#less-options]
Support for "javascriptEnabled" may be removed from the Angular CLI starting with Angular v19.
The plugin "angular-less" was triggered by this import
angular:styles/global:styles:1:8:
Environment
Description
Currently the library's less files are depending on
javascriptEnabled
option inless-loader
config, unfortunately due to security issues this feature was deprecated long ago...I have seen that Angular still uses this flag in his default Webpack config for less but going forward I guess it is a good idea to remove as I am not sure how long it will keep being supported (it is no longer works with higher
less-loader
versions...).Currently it is blocking me from creating custom themes, which really pull me back from using this awesome library, I will be glad if you could fix that soon...
The text was updated successfully, but these errors were encountered: