<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>npm on Ravener</title><link>https://ravener.is-a.dev/tags/npm/</link><description>Recent content in npm on Ravener</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 02 Sep 2026 10:13:28 +0500</lastBuildDate><atom:link href="https://ravener.is-a.dev/tags/npm/index.xml" rel="self" type="application/rss+xml"/><item><title>Best Practices for publishing to NPM</title><link>https://ravener.is-a.dev/posts/npm-best-practices/</link><pubDate>Wed, 02 Sep 2026 10:13:28 +0500</pubDate><guid>https://ravener.is-a.dev/posts/npm-best-practices/</guid><description>So, you are thinking of publishing a package on the npm registry?
Here are some best practices that may not be so obvious at a glance but I&amp;rsquo;ve learned with experience.
Include only the files you need You can add the following inside your package.json
{ &amp;#34;files&amp;#34;: [ &amp;#34;dist&amp;#34; ] } This is assuming you are using TypeScript and have a dist/ folder, this can be your src/ folder if you are using plain JavaScript.</description></item></channel></rss>