<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Brittany</title>
    <description>The latest articles on DEV Community by Brittany (@only8britt).</description>
    <link>https://dev.to/only8britt</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F142160%2Fcc88a496-7512-4c3f-8037-d62913325c1c.jpeg</url>
      <title>DEV Community: Brittany</title>
      <link>https://dev.to/only8britt</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/only8britt"/>
    <language>en</language>
    <item>
      <title>Poll: Do you read the question or answers first on Stackoverflow? </title>
      <dc:creator>Brittany</dc:creator>
      <pubDate>Tue, 24 Sep 2019 00:10:27 +0000</pubDate>
      <link>https://dev.to/only8britt/poll-do-you-read-the-question-or-answers-first-on-stackoverflow-4g5j</link>
      <guid>https://dev.to/only8britt/poll-do-you-read-the-question-or-answers-first-on-stackoverflow-4g5j</guid>
      <description>&lt;p&gt;Just curious, when you're searching for an answer on Stackoverflow, do you take the time to read the original question at the top of the page thoroughly or go straight to the answers at the bottom? &lt;/p&gt;

&lt;p&gt;I will usually quickly scan over the question just to see if it's vaguely related to what I'm looking for, then look at the answers, and then usually have to go back to the question at the top. 😂&lt;/p&gt;

</description>
      <category>stackoverflow</category>
      <category>discuss</category>
      <category>watercooler</category>
    </item>
    <item>
      <title>ReferenceError: primordials is not defined</title>
      <dc:creator>Brittany</dc:creator>
      <pubDate>Fri, 16 Aug 2019 03:17:36 +0000</pubDate>
      <link>https://dev.to/only8britt/referenceerror-primordials-is-not-defined-140a</link>
      <guid>https://dev.to/only8britt/referenceerror-primordials-is-not-defined-140a</guid>
      <description>&lt;p&gt;I've started to work on a project that I haven't really touched since 2017. As you can imagine, I'm getting tons of warnings due to all of my node packages being outdated. &lt;/p&gt;

&lt;p&gt;When trying to run &lt;code&gt;npm install&lt;/code&gt; or &lt;code&gt;npm update&lt;/code&gt; this is one of the errors I was getting.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;const { Math, Object } = primordials;
                         ^

ReferenceError: primordials is not defined
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;What does this even mean?? &lt;/p&gt;

&lt;p&gt;After some google searching, I saw that a lot of people were getting this error because they were running a version of Gulp that was incompatible with their current node version. &lt;/p&gt;

&lt;p&gt;"Okay... cool. But I don't have Gulp installed! :&amp;lt; " &lt;br&gt;
-me &lt;/p&gt;

&lt;p&gt;I spent about 45mins-1hr trying to get rid of this error, but the thing that did it was removing &lt;code&gt;sequelize-cli&lt;/code&gt; from my list of dependencies. &lt;/p&gt;

&lt;p&gt;How did I realize that &lt;code&gt;sequelize-cli&lt;/code&gt; was the source of the problem? &lt;/p&gt;

&lt;p&gt;I deleted my &lt;code&gt;node_modules&lt;/code&gt; folder and ran &lt;code&gt;npm install&lt;/code&gt; because I had no idea what to do next and was trying anything I could think of.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight"&gt;&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Brittanys-MacBook-Pro-4:Gabble_Forum britthome$ npm install
npm WARN deprecated gulp-util@3.0.8: gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated natives@1.1.6: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;p&gt;AND WHAM-O! Look at that. &lt;code&gt;gulp-util&lt;/code&gt; you sneaky devil. I was really confused and searched my entire directory for that dependency but couldn't find it. That's when I got the idea that one of my listed dependencies must depend on Gulp. &lt;/p&gt;

&lt;p&gt;I went to the npm website and searched for all of my dependencies one by one. On each package's page, you can see what packages it depends on. &lt;code&gt;sequelize-cli&lt;/code&gt; was of course, my last listed package, but when I finally got to it, I saw that it does depend on Gulp. &lt;/p&gt;

&lt;p&gt;So, what's next? &lt;/p&gt;

&lt;p&gt;Because I created this project so long ago, I don't remember the necessity of each dependency, so I'm in the process of learning about each one and deciding if I really need it or not. Because I'm using &lt;code&gt;sequelize&lt;/code&gt;, I imagine that I'll need some sort of CLI, but maybe there is a native CLI with the package or another package I can use? Maybe I won't even use &lt;code&gt;sequelize&lt;/code&gt;. SO MANY DECISIONS! &lt;/p&gt;

&lt;p&gt;Just wanted to share this little experience. Hopefully, it helps someone. &lt;/p&gt;

</description>
      <category>webdev</category>
      <category>npm</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
