<?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: Sherin</title>
    <description>The latest articles on DEV Community by Sherin (@cadoangelus).</description>
    <link>https://dev.to/cadoangelus</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%2F74541%2F683351c9-1782-4cda-af98-2c7d81acfaab.png</url>
      <title>DEV Community: Sherin</title>
      <link>https://dev.to/cadoangelus</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/cadoangelus"/>
    <language>en</language>
    <item>
      <title>Package name in a new Flutter project</title>
      <dc:creator>Sherin</dc:creator>
      <pubDate>Thu, 15 Aug 2019 08:46:50 +0000</pubDate>
      <link>https://dev.to/cadoangelus/package-name-in-a-new-flutter-project-3jml</link>
      <guid>https://dev.to/cadoangelus/package-name-in-a-new-flutter-project-3jml</guid>
      <description>&lt;p&gt;If you are someone like me, who uses Visual Studio Code to work with Flutter, you would most likely be using Flutter CLI to create new flutter projects.&lt;/p&gt;

&lt;p&gt;Flutter CLI, by default, would use &lt;code&gt;com.example.project_name&lt;/code&gt; as your package name/bundle identifier. If you want to specify to change that behaviour, you can run&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;code&gt;flutter create --org com.my_cool_org project_name&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;This would set the Android package name to &lt;code&gt;com.my_cool_org.project_name&lt;/code&gt; and iOS bundle identifier to &lt;code&gt;com.myCoolOrg.projectName&lt;/code&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
    </item>
    <item>
      <title>exports vs module.exports in Node.js</title>
      <dc:creator>Sherin</dc:creator>
      <pubDate>Sun, 09 Jun 2019 12:54:38 +0000</pubDate>
      <link>https://dev.to/cadoangelus/exports-vs-module-exports-in-node-js-2ln5</link>
      <guid>https://dev.to/cadoangelus/exports-vs-module-exports-in-node-js-2ln5</guid>
      <description>&lt;div class="highlight"&gt;&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="nx"&gt;exports&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;id&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="c1"&gt;//this is ok&lt;/span&gt;

&lt;span class="nx"&gt;exports&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;};&lt;/span&gt; &lt;span class="c1"&gt;//this is not ok&lt;/span&gt;

&lt;span class="nx"&gt;module&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;exports&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="na"&gt;id&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;};&lt;/span&gt; &lt;span class="c1"&gt;//this is ok&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;



&lt;h2&gt;
  
  
  WHY?
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;exports&lt;/code&gt; is simply a variable reference to &lt;code&gt;module.exports&lt;/code&gt;. So we can change the properties of the &lt;code&gt;exports&lt;/code&gt; object, but if we change the whole object, it would no longer be a reference to &lt;code&gt;module.exports&lt;/code&gt;&lt;/p&gt;

</description>
      <category>node</category>
      <category>exports</category>
    </item>
    <item>
      <title>Check whether a dependency is installed in your Node.js app</title>
      <dc:creator>Sherin</dc:creator>
      <pubDate>Sun, 09 Jun 2019 11:52:56 +0000</pubDate>
      <link>https://dev.to/cadoangelus/check-whether-a-dependency-is-installed-in-your-node-js-app-29ee</link>
      <guid>https://dev.to/cadoangelus/check-whether-a-dependency-is-installed-in-your-node-js-app-29ee</guid>
      <description>&lt;p&gt;You can use &lt;strong&gt;require.resolve()&lt;/strong&gt; to check whether a dependency is available in your Node.js app without loading it. You can read more about it &lt;a href="https://nodejs.org/api/modules.html#modules_require_resolve_request_options"&gt;here&lt;/a&gt;&lt;/p&gt;

</description>
      <category>node</category>
    </item>
    <item>
      <title>Building your application after pushing to Heroku</title>
      <dc:creator>Sherin</dc:creator>
      <pubDate>Wed, 03 Apr 2019 02:20:27 +0000</pubDate>
      <link>https://dev.to/cadoangelus/building-your-application-after-pushing-to-heroku-4m1o</link>
      <guid>https://dev.to/cadoangelus/building-your-application-after-pushing-to-heroku-4m1o</guid>
      <description>&lt;p&gt;When deploying their application to Heroku, most people will run development script for their application. This will tremendously increase the loading time of your application. Instead you can build a production-ready version of your application after pushing your application to Heroku making use of &lt;strong&gt;heroku-postbuild&lt;/strong&gt; script in your &lt;strong&gt;package.json&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>heroku</category>
      <category>npm</category>
    </item>
  </channel>
</rss>
