<?xml version="1.0" encoding="UTF-8"?> 
<rss version="2.0"
        xmlns:content="http://purl.org/rss/1.0/modules/content/"
        xmlns:wfw="http://wellformedweb.org/CommentAPI/"
        xmlns:dc="http://purl.org/dc/elements/1.1/"
        xmlns:atom="http://www.w3.org/2005/Atom"
        xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
        xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
        >
<channel>
  <title>asgaard</title>
  <description>Npm</description>
  <link>https://blog.asgaard.co.uk/t/npm</link>
  <lastBuildDate>Wed, 22 Apr 26 11:35:28 +0000</lastBuildDate>
  <language>en</language>
  <count>1</count>
  <offset>0</offset>
      <item>
    <title>npm is terrible</title>
    <link>https://blog.asgaard.co.uk/2017/08/02/npm-is-terrible</link>
    <pubDate>Wed, 02 Aug 17 08:49:46 +0000</pubDate>
    <guid>https://blog.asgaard.co.uk/2017/08/02/npm-is-terrible</guid>
    <description><![CDATA[
<p>
It&#039;s hard for me to believe in the quality of a piece of software that behaves like this:<pre>
$ npm install [package]
  npm <span style='color: #800000'>ERR!</span> Please try running this command again as root/Administrator. 
$ npm install [package]
  (OK)
</pre>
<p>
I&#039;m sure about five years ago npm was a useful and reliable piece of software. Perhaps I remember incorrectly.
<p>
I had another tale of npm woe last week when after runing `npm install`, my node_modules/package-name was a symlink to none other than node_modules/package-name. For some reason, downgrading npm to version 3 (from version 5) made it all work properly.
<p>
I groaned today when I had to install yarn, yet another package manager, to install something else, but the sooner something sane replaces npm the better.
<p>
[...]]]></description>
    <content:encoded><![CDATA[
<p>
It&#039;s hard for me to believe in the quality of a piece of software that behaves like this:<pre>
$ npm install [package]
  npm <span style='color: #800000'>ERR!</span> Please try running this command again as root/Administrator. 
$ npm install [package]
  (OK)
</pre>
<p>
I&#039;m sure about five years ago npm was a useful and reliable piece of software. Perhaps I remember incorrectly.
<p>
I had another tale of npm woe last week when after runing `npm install`, my node_modules/package-name was a symlink to none other than node_modules/package-name. For some reason, downgrading npm to version 3 (from version 5) made it all work properly.
<p>
I groaned today when I had to install yarn, yet another package manager, to install something else, but the sooner something sane replaces npm the better.
<p>
]]></content:encoded>
  </item>
  </channel>
</rss>