This is VanillaJS (unmodified):
// VanillaJS v1.0
// Released into the Public Domain
// Your code goes here:
As you can see, it's not really a framework or a library. It's just a running gag for framework-loving bosses or people who think you NEED to use a JS framework. It means you just use whatever your (for you own sake: non-legacy) browser gives you (using Vanilla JS when working with legacy browsers is a bad idea).
Answer from ThiefMaster on Stack OverflowVideos
» npm install vanilla-javascript
This is VanillaJS (unmodified):
// VanillaJS v1.0
// Released into the Public Domain
// Your code goes here:
As you can see, it's not really a framework or a library. It's just a running gag for framework-loving bosses or people who think you NEED to use a JS framework. It means you just use whatever your (for you own sake: non-legacy) browser gives you (using Vanilla JS when working with legacy browsers is a bad idea).
Using "VanillaJS" means using plain JavaScript without any additional libraries like jQuery.
People use it as a joke to remind other developers that many things can be done nowadays without the need for additional JavaScript libraries.
Here's a funny site that jokingly talks about this: http://vanilla-js.com/
» npm install vanilla-js
» npm install @stytch/vanilla-js
I'm writing a node application to download files given paths (it could be in http, https, ftp, sftp). Since, the protocols could be added later, I'm trying to do it in a generic and scalable way with as little libraries as possible.
I have looked into some S/O questions but some of them require http modules to work with or some require axios or third-party libs. I also tried to use net.Socket but it doesn't seem to be the correct way to do it.
So, I'm wondering if there're generic ways to achive this? fs and other vanilla node modules are fine.
Thanks!