Warnings in latest release

Radzen Studio Angular
1

I get warnings (since todays released version) everytime I am building the app.
Every request on the running application writes it into my browsers console too, which is a bit anoying while debugging.

WARNING in (webpack)/buildin/global.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Program Files\Radzen\resources\node_modules\webpack\buildin\global.js
    Used by 2 module(s), i. e.
    C:\Program Files\Radzen\resources\node_modules\punycode\punycode.js
  • c:\Program Files\Radzen\resources\node_modules\webpack\buildin\global.js
    Used by 5 module(s), i. e.
    c:\dev\Manager\client\node_modules@angular\core\esm5\core.js
    @ (webpack)/buildin/global.js
    @ C:/Program Files/Radzen/resources/node_modules/punycode/punycode.js
    @ C:/Program Files/Radzen/resources/node_modules/url/url.js
    @ ./node_modules/webpack-dev-server/client?http://0.0.0.0:0
    @ multi webpack-dev-server/client?http://0.0.0.0:0 ./src/main.ts

WARNING in (webpack)/buildin/module.js
There are multiple modules with names that only differ in casing.
This can lead to unexpected behavior when compiling on a filesystem with other case-semantic.
Use equal casing. Compare these module identifiers:

  • C:\Program Files\Radzen\resources\node_modules\webpack\buildin\module.js
    Used by 1 module(s), i. e.
    C:\Program Files\Radzen\resources\node_modules\punycode\punycode.js
  • c:\Program Files\Radzen\resources\node_modules\webpack\buildin\module.js
    Used by 1 module(s), i. e.
    c:\dev\Manager\client\node_modules\moment\moment.js
    @ (webpack)/buildin/module.js
    @ C:/Program Files/Radzen/resources/node_modules/punycode/punycode.js
    @ C:/Program Files/Radzen/resources/node_modules/url/url.js
    @ ./node_modules/webpack-dev-server/client?http://0.0.0.0:0
    @ multi webpack-dev-server/client?http://0.0.0.0:0 ./src/main.ts
2

Looks like you've executed npm install in some of your applications client folder while the symlink created by Radzen was present. This unfortunately corrupted the node_modules installed initially by Radzen and the only option is to reinstall Radzen.

3

Well, that actually happened, uninstalling and installing again solved the issue (had to restart the machine to). Thank you.