refactor: Optimize console removal and simplify github-slugger usage

Author: codebucks27

next.config.js

@@ -2,7 +2,7 @@
 module.exports = {
     // othor next config here...
     compiler: {
-      removeConsole: true,
+      removeConsole: process.env.NODE_ENV === 'production' ? true : false,
     },
     webpack: config => {
       config.plugins.push(new VeliteWebpackPlugin())

src/app/categories/[slug]/page.js

@@ -1,9 +1,9 @@
 import { blogs as allBlogs } from "@/.velite/generated";
 import BlogLayoutThree from "@/src/components/Blog/BlogLayoutThree";
 import Categories from "@/src/components/Blog/Categories";
-import GithubSlugger, { slug } from "github-slugger";
+import { slug } from "github-slugger";
 
-const slugger = new GithubSlugger();
+// const slugger = new GithubSlugger();
 
 export async function generateStaticParams() {
   const categories = [];
@@ -12,7 +12,7 @@ export async function generateStaticParams() {
   allBlogs.map((blog) => {
     if (blog.isPublished) {
       blog.tags.map((tag) => {
-        let slugified = slugger.slug(tag);
+        let slugified = slug(tag);
         if (!categories.includes(slugified)) {
           categories.push(slugified);
           paths.push({ slug: slugified });