Describe the bug
I have analyzed the dependencies of my backend app and the single biggest dependency is 'chromedriver', which obviously is strange in a backend app.
npm ls chromedriver
ba-fem-nx-workspace@1.0.0 C:\Users\andymel\_d_a_t_e_n\programmieren\_repos\amc-nx-workspace
└─┬ nest-keycloak-connect@2.0.0-alpha.2
└─┬ keycloak-connect@26.1.1
└── chromedriver@129.0.0
I guess it is used for testing and should be moved into the devDependencies?
Version
26.1.1
Expected behavior
Per default no install of chromedriver in production apps
Actual behavior
Using keycloak-connect leads to chromedriver being 18.1MB of your backend app
(and maybe to problems as chromedrive binaries maybe can not be installed in the specific environment?!)
How to Reproduce?
Use keycloak-connect in your app, build it and analyse the node_modules folder for example with
du -sh * | sort -h
Anything else?
No response
Describe the bug
I have analyzed the dependencies of my backend app and the single biggest dependency is 'chromedriver', which obviously is strange in a backend app.
I guess it is used for testing and should be moved into the devDependencies?
Version
26.1.1
Expected behavior
Per default no install of chromedriver in production apps
Actual behavior
Using keycloak-connect leads to chromedriver being 18.1MB of your backend app
(and maybe to problems as chromedrive binaries maybe can not be installed in the specific environment?!)
How to Reproduce?
Use keycloak-connect in your app, build it and analyse the node_modules folder for example with
du -sh * | sort -hAnything else?
No response