Saumya

In package.json there is a script section. From here one can run NPM Scripts. "scripts": { "one": "scriptOne.js", "two": "scriptTwo.js" } These can be run like this. npm run one This particular line will run scriptOne.js. This is powerful as we could take Node’s power and run any automated task for ourselves. At first this seemed simple to me. Soon I came across cross-platform bugs. Since we are writing this in JS, it could be run anywhere Node is available.

We will be talking about Windows 11 and NeoVIM. It can be seen as general Windows not specific to Windows 11, since I have done it in Windows 11, thought would mention it here in order to avoid the confusion. On Windows machines I avoided configuring or even using NeoVIM. Thought it would be much more painful here as compared to Linux. So started using NeoVIM on WSL. Configured and ready within a couple of minutes as that is basically all Linux.

Configuring NeoVIM is straight forward. All one need to know is, where to put what. Here is a list of references to get started with it. For me, it was not difficult as I just needed a decent text editor with a file tree. All I did is pull the respective github repos into the folder and call them from init,lua. This is nice and fine but since the configuration is too easy and Lua just feels good to play with, thinking of confuguring it further and play with plugin managers.

I never thought, the day will come! The story of VIM addiction and NeoVIM adoption. In search of a code editor which is available everywhere, from Desktop to servers, I accidentally got used to vi some years back. I had to edit some files on the server or they call it Cloud, the only editor available there was vi. I just used it and forgot it as it was not even close to anything that modern code editors offer.

Is it a library or a framework?! Do not know, but everyone is using it. Must be good. Hype Driven Development. It should be a known story for experienced developers. For new developers it is alright to start here. The problem is never the tool itself. How it is been used, the implementation details. That is the place, where it matters. During the last days of FlashPlayer, the company and the community both jumped into Flex, the framework and the tool-chain to say, everything can be fixed with it!