2 ms·
* on the command line * in your text editor, for example in VS Code * in for your build tool, for example in webpack * via the Node.js API * as a PostCSS pl
by monkeynotes 8y ago
* on the command line
* in your text editor, for example in VS Code
* in for your build tool, for example in webpack
* via the Node.js API
* as a PostCSS plugin
^ If I was trying to meet compatibility with the above requirements I'd probably pick JS too.
It's easy to complain about npm but the fact is it get so much done every day. I don't want to be compiling binaries and all the compatibility crap that goes on there. I have no problem with well written JS or Typescript.
Yes NPM dependency can be a bit crazy, but it doesn't pollute your system. Using nvm everything is contained in a modules directory. I can literally delete that folder and be back to square one in two seconds flat. Compiling binaries, well, that's where I feel like you end up pulling your hair out.
I have to compile binaries for a certain version of a capybarra gem, to do that I had to roll back x-code. Never had to do anything like that for a straight forward npm.