3 Matching Annotations
- Sep 2021
The main reason I love Node.js is that I don’t have to deal with the awfulness that is JS front-end tooling.
Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.
more trouble than it's worth
- creating more complexity than it cured
- Why can't this be easier/simpler? Why does it have to be so hard/complicated?
- changed their mind/opinion
- too hard/complicated/non-trivial
- removing feature that is more trouble than it's worth (not worth the effort to continue to maintain / fix bugs caused by keeping it)
- more trouble than it's worth
- doing more harm than good
- newer/better ways of doing things
- too complicated
It seems to me (N.b. what do I know about this? Nothing!) that the best solution would be to tweak the 'Change Password' process so that it also updates the 'Passwords and Keys'>Passwords>Login folder's properties.
"I'm not an expert, but it seems to me..."