I’m getting too old for this shit

I’ve started a new project. A Visual Studio 2019 .Net Core application with React+Redux. A template application. Since, for jodiBooks, we’d already worked with react-native in combination with redux, I didn’t expect this to be a big deal. But.. fuck me, I already hate this. I really miss the NuGet package manager. Just right-click, search and install the library you want.

But now? Oh, no, forget it. The open source mess that is JavaScript web development is now at my door step. It’s scripts that don’t work left and right. I Google how to add an npm package and find a promise of right-clicking in Visual Studio to add an npm package. It is a lie. The icon that is shown in the screenshot isn’t present in my project you fuckers! I have a different project template and it isn’t what you’re showing in your little Hello World playground project.

One of the first things I want to do, is attach the new application to our existing Web API. No big deal, just fetch a url. Except I don’t want that hardcoded, obviously, I want a config file. Something similar to Web.config. A confi–.. A conf— hello? Where can I… No? Oh… I have to install a library to do that. Webpack.. sure.. fine. I’ll install it. Update the URL. And refresh my browser. And nothing happens. Nothing. Nothing!

You know why? Because whoever designed this shit thought it convenient to have to type dotnet run every single fucking time you want to run the application. Or you have to publish. Do you know how convenient that is? It isn’t! It isn’t!

And you know what happens when I publish? You know what happens after I added a package with npm, added a webpack.config.js file and then publish?

And you know what the error is, for a clean project in which I did nothing except install webpack and point to a different API url?

The react-scripts package provided by Create React App requires a dependency:
“webpack”: “blah”
Don’t try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree

And you know what happens if I remove webpack again and then try to publish again, something that worked before I added webpack??

This image has an empty alt attribute; its file name is image-1.png

The react-scripts package provided by Create React App requires a dependency:

“eslint”: “^6.1.0”

Don’t try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:

What the…? Fuck, I feel old.

0 Replies to “I’m getting too old for this shit”