|
|
|
npm in a git world
Monday, December 4 2017
Towards the end of the day, I put some effort into trying to get a basic "Hello World" type charts.js graph to work on my local system. In the past, when trying to install such a Javascript library, the installation would've been easy. I'd download some directory, and put it in some place in my file system, and then give a suitable src attribute in an HTML script tag where I wanted to use the library. These days, though, it's not so easy. One is expected to use a command-line tool such as npm that goes out on the internet and somehow downloads the library, does some stuff to it, and then it supposedly works on your computer. But what if npm is installing the Javascript into a directory managed by the git repository system? Is npm configuring things with absolute addresses? Who the fuck knows; the whole system seems designed not to be transportable. And I need it to be transportable, to work in whatever level of directory nesting it finds itself. To ensure that this was the case, I was forced to use npm initially to get the software onto my computer (downloading the code from github had produced unusable code). Once there, I moved it to a new location on my computer and tweaked the script tags until it started working. Once it did, I could be sure that when git copied it live, it would continue to do so.
In other news, Gretchen was up in Albany today to have what remain of her lady parts looked at. She returned with a clean bill of health, though she of course fucked with me initially by lying that the doctor had looked at the stitches and decided they needed more time to heal. While in Albany, Gretchen spent some time and money at the Honest Weight Food Co-op, returning with all the things they sell that we love (such as big tubs of tempeh "chicken" salad). [REDACTED]
For linking purposes this article's URL is:
http://asecular.com/blog.php?171204 feedback
previous | next |
