Table of Contents
Introduction
It is sometimes true that when you are bringing javascript into the world, you can tell that this particular javascript is perhaps not to have a happy life.
However, by utilizing the fundamentals of package management, you can divest yourself of this burden just a little. You see: your Stack may runneth over, your dependencies may resemble a knotted hair-net, and you will borrow and steal until you have at last written as little javascript as possible, which is after all the goal. Clamber up the shoulders of giants, that you might see the ships in the harbor! Why, when we were ourselves a boy, we did just that. Somehow we kicked our uncle in the eye in doing so; — he was half-blind for weeks and never quite forgave me. But, then, no one ever said that standing on the shoulders of giants, or for that matter regular-sized adults, would be altogether nonviolent. No one, we think, likes to be used as a stepladder, however noble your purpose. Nor in our experience will they stand still long enough for you to set up a proper ladder next to them.
You, the reader, have embarked on a journey which will send you wandering in the fresh cut fields alongside the shaggiest of shaggy dog scripting languages, and we are to be your scientifick guide. It has admittedly been some time since we were last able to impart our favorite tips and tricks, but we have been brooding on them like a good mother hen; — rejoice, for the javascript is upon us. We will install Node.js, and we will avoid indigestion. Well, one or the other, at least.
Prerequisites
We should have mentioned: there are no prerequisites to this tutorial save for having given much thought to one’s own life up to now, and to have given due thought to one’s parents’ lives, and to one’s uncle’s lives, depending on how many uncles one has had; — as well as to have considered the entire history of computing, how it was invented and made real over so many years, how it came to displace so many of our animal spirits, and, not least, how your own computer, on which you read this very text, journeyed to your home from wherever it was begot. Pray, how might your life have been different if you had never come into contact with a computer such as this one? we tremble to think that you will never know.
At this point you will have set down a fine foundation for the tutorial and may continue.
Although, we beg your pardon, one small detail, you must first install *Linux* upon the computer. In truth we nearly forgot this part. When we were in the late spring of our youth, we had our own "year of Linux on the desktop" if you take our meaning. It’s just– we worry, really we worry, that so many such meditations on sowing Linux in one’s garden, one’s computer garden, can be perhaps a little too terse. we maintain here that one ought to know the whole of Linux, its whole prelude and such.
The story, as it has been told to me, takes us back to a venture called Bell Laboratories, which we have always thought especially precious, imagine a laboratory dedicated to—
Note: This part of the original manuscript was destroyed and cannot be reproduced here.
Step 1 — Steeling One’s Loins to Install Node.js
Thus,— thus our fellow laborers and associates in this great harvest of our learning, we shall ready ourselves to ready ourselves to ready ourselves to run javascript from the command line.
It strikes me, though, that these "command lines" have an almost martial character. Now, we may not have any military experience per se, but we have listened to our uncle talk about his military service a very great deal, so it seems to me that we are qualified to comment on this subject.
But we are getting ahead of ourselves. we remember one day when Uncle was expounding on the best ways of structuring a command line in order to discourage its little soldiers from running away en masse… On that day we were afflicted with the most grievous rash! But as it had little to do with our endeavors on the computer we shall, in turn, endeavor not to worry you with the rash’s tale.
Anyhow, we were about to expiate the finer points of customizing one’s terminal … when we found we could not focus our mind for any length of time away from that pitiable rash. we remember our eldest brother developed a rash which at least a little resembled this one the first time he was away from the family estate on business.
We believe it would be a mistake to assume our brother’s rash did not, in some way, prefigure javascript.
Step 2 — Appraising the Essential Qualities of Node.js
We do quite like the semicolons.
We think javascript has an essentially obliging quality, always to politely let variables be something or other. To each variable its declaration; nothing is implicit. Good, good. Of course, if they are not let, they are constant — but then, constancy is not always the virtue that it imagines itself to be. To be trapped with an unchanging variable is, amen, not so unlike being trapped in a marriage, which is what became of our great-uncle. Really it took the spirit out of him over so many years… we think he felt quite diminished, constantly having to pay his wife’s debts by returning over and over to his most famous acting role: the rear end of a pantomime horse. But imagine if he were trapped in a variable declaration! Imagine his little squeaking voice… "help, we’re down here in this lodash, someone get me out, help, help!"
This is improved if you imagine doing the voice out of the little corner of your mouth.
We must also note here that we find the inconsistent application of require strict; in modern-day — was it — *eczema script*, terribly vexing. The incantation is admirable, enough on its own to keep me a-going; would that we had all had such a firm hand taken with us. In fact we chanced recently to be walking to our uncle's office alongside a neighbor woman whose schoolboy son was with her and who would not stop pelting me with rocks, and we offered that she might require strict; with the lad.
Warmly (somewhat), she said to me, go away. we wonder if perhaps we were not in the right there.
Step 3 — Thinking About Your Mother
Of course you ought not let the javascript appear to you as some dismal Scheherazade, stewarding you through memory; — some indulgence, granted, is unavoidable. we, for example, dream of being able to speak with our mother’s midwife at the moment of our deliv’rance, to say: "look! That’s me over there! we’re a baby!"
We are much aware that javascript’s history — much like our own history — is chock-a-block with naysayers, who are ready to list at a moment’s notice all of the vocations to which it is ill-suited. To them I say, if javascript can run on the command line, why not invent time travel using javascript?
Points in its favor are thus:
- No one else has invented it so far, therefore this approach must be at least as good.
- We know this language already and we don’t want to learn another one.
So far it has been surprisingly challenging to raise sufficient venture capital on our family estate in order to hire javascript developers for this project of ours; everyone seems mostly to want to talk about real estate, or tulip futures. Alas, the technickal industry is quite competitive.
Now, as we had already been at pains, earlier in this tutorial, to impart the right state of mind for installing Node.js, we trust that state of mind will linger a while yet, and we might be afforded a tiny detour.
Step 4 — Some Brief Opinions on Package Management
We understand that Node.js has its own package manager.
Personally, we like to imagine this so-called "package manager" as a faithful homunculus, fetching software and other sundries from the shop down the street, save for that the street is also in the computer, and the shop makes no money at all. npm is his name, and thusly: "En-pee-em!" we screech and beckon, as ours own father might’ve at day laborers. "En-pee-em!"
Sometimes En-pee-em returns me the wrong library, and while our mind fills with thoughts of retribution, instead we remind ourselves, we must learn his hermeneutic ways, we must make our own way in the world. Recently we had a terrible episode;— he was making pitiful excuses about how some new wondrous physick had to be "installed globally," and all at once we were consumed instead by dark thoughts of Uncle. Nothing would have sated him more than to have installed himself globally in his many trades!
As the reader has already learnt so much about javascript in this tutorial, perhaps they would instead like to consider the many ideas we have had for En-pee-em and we to go on wild adventures together. For one, we have never been to France, though we haven’t yet decided if we would like to visit.
Summarily, though, we would like to have En-pee-em take one of our own javascript packages to the shop someday, to share with others.
Conclusion
We have agreed to no such "conclusion."
Note: In order to install Node.js, please refer to the work of the cloud provider’s other authors.
