Merge pull request #331 from Shramkoweb/feat/add-article-about-pnpm

Feat/add article about pnpm

_posts/pnpm.md

@@ -0,0 +1,135 @@
+---
+title: "How to Migrate Your Project from npm to pnpm and save 44% deployment time: A Step-by-Step Guide"
+heading: How decrease deployment time by 44% with pnpm
+description: Learn how to efficiently migrate your project from npm to pnpm with our comprehensive step-by-step guide.
+createDate: 2024-06-16T21:34:24.323Z
+keywords: [ migrate npm to pnpm, pnpm migration guide, npm to pnpm transition, pnpm benefits, pnpm installation, pnpm tutorial, npm alternatives, efficient package management, pnpm setup, node.js package manager, npm vs pnpm, upgrading to pnpm, pnpm step-by-step guide ]
+categories: [ Project-Setup, How-To, JS, TS, Node ]
+featured: true
+---
+
+## Introduction
+
+<Image src="pnpm-logo.png" alt="pnpm logo on gay background" />
+
+I found article from Vercel
+about [Projects using pnpm can now be deployed with zero configuration](https://vercel.com/changelog/projects-using-pnpm-can-now-be-deployed-with-zero-configuration)
+and I wanted to try it.
+
+## Why Migrate to pnpm?
+
+Before diving into the migration process, it’s important to understand why pnpm is beneficial:
+
+1. **Speed** 🚀: pnpm installs dependencies faster than npm by using a unique package linking mechanism.
+2. **Disk Space** 🔎: It saves disk space by using a global store and hard links.
+3. **Consistency** 💡: pnpm ensures that dependencies are installed in a way that is more consistent with the version
+   specified in your `package.json`.
+
+## Installation of pnpm
+
+First, you need to install pnpm globally. You can do this by running:
+
+```bash
+brew install pnpm
+```
+
+## Migration Steps
+
+### 1. Clean the Project
+
+Remove the `node_modules` directory and the `package-lock.json` file. This step is crucial to ensure that there are no
+leftover artifacts from npm that might interfere with pnpm.
+
+```bash
+rm -rf node_modules package-lock.json
+```
+
+### 2. Initialize pnpm
+
+Run the following command to initialize pnpm in your project directory:
+
+```bash
+pnpm install
+```
+
+This command will create a `pnpm-lock.yaml` file and install all the dependencies listed in your `package.json`.
+
+### 3. Verify Dependency Installation
+
+Check that all dependencies have been installed correctly by running:
+
+```bash
+pnpm list
+```
+
+This command lists all the installed dependencies and their versions. Make sure that there are no missing or outdated
+packages.
+
+<Image src="pnpm-list.png" alt="pnpm list command result in terminal" />
+
+## Updating Scripts
+
+### 1. Update npm Scripts
+
+In your `package.json`, update any npm scripts to use pnpm where necessary. For example, if you have a script for
+installing dependencies, change it from:
+
+```json
+"scripts": {
+"install": "npm install"
+}
+```
+
+to:
+
+```json
+"scripts": {
+"install": "pnpm install"
+}
+```
+
+### 2. Update CI/CD Pipelines
+
+If your project uses CI/CD pipelines, ensure that the build scripts and installation commands are updated to use pnpm.
+For example, in a [GitHub Actions  with pnpm](https://pnpm.io/continuous-integration) workflow, you might update the
+step as follows:
+
+```yaml
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: pnpm/action-setup@v4
+        with:
+          version: 9
+      - uses: actions/setup-node@v4
+        with:
+          node-version: ${{ matrix.node-version }}
+          cache: 'pnpm'
+      - name: Install
+        run: pnpm i
+      - name: Run Tests // All your CI commands
+        run: pnpm run test
+```
+
+## Handling Issues and Troubleshooting
+
+During the migration, you might encounter some issues.
+
+> Error: Unable to locate executable file: pnpm. Please verify either the file path exists or the file can be found
+> within a directory specified by the PATH environment variable. Also check the file mode to verify the file is
+> executable.
+
+I stuck with this error when I tried to run the `pnpm` command in GitHub Actions.
+
+The solution was to use the `pnpm/action-setup@v4` before `actions/setup-node@v4`.
+So simply just copy the [above code](#2-update-cicd-pipelines) and paste it in your `.yml` file.
+
+## Conclusion
+
+This migration helped me to reduce the time of deployment by **44%** and the size of `node_modules` by **5%**.
+
+<Image src="vercel-deployment.png" alt="Deployment time on vercel dashboard. Around 1 seccond" />
+
+More info how my blog works you can find there [How my site works under the hood](./introducing-the-new-shramko.dev)

_posts/unsubscribe-immediately.md

@@ -5,7 +5,7 @@ heading: Unsubscribe from Email Newsletters Immediately
 createDate: 2024-04-08T11:47:44.249Z
 keywords: [ Unsubscribe from email newsletters, Turn off notifications, Email management tips, Notification management, Email overload, Focus improvement ]
 categories: [ Opinion, Productivity, Habits, Tools ]
-featured: true
+featured: false
 ---
 
 Small tasks that we put off can accumulate and ultimately consume much more of our time and energy. One such small yet important task is unsubscribing from annoying email newsletters and notifications.

components/mdx-components/index.tsx

@@ -9,7 +9,7 @@ function CustomLink(
   AnchorHTMLAttributes<HTMLAnchorElement>,
 ) {
   const { href, children, className } = props;
-  const isInternalLink = href && (href.startsWith('/') || href.startsWith('#'));
+  const isInternalLink = href && (href.startsWith('/') || href.startsWith('.') || href.startsWith('#'));
 
   if (isInternalLink) {
     return (

package.json

@@ -5,13 +5,13 @@
   "scripts": {
     "article": "node lib/scripts/generate-article-template.js",
     "build": "prisma generate && next build",
-    "dev": "next dev --turbo",
+    "dev": "next dev",
     "lint": "next lint",
     "lint:fix": "next lint --fix",
     "postbuild": "next-sitemap",
     "postinstall": "prisma generate",
     "pre-commit": "",
-    "pre-push": "npm run lint",
+    "pre-push": "pnpm run lint",
     "prepare": "git config core.hooksPath .git-hooks",
     "start": "next start",
     "test": "jest --watch",