Yaz\u0131l\u0131m projelerinizde biriken ve performans\u0131 d\u00fc\u015f\u00fcren kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar\u0131 tespit etmenin ve temizlemenin en etkili yollar\u0131n\u0131 ke\u015ffedin. Projenizi hafifletin, g\u00fcvenli\u011fi art\u0131r\u0131n ve geli\u015ftirme s\u00fcre\u00e7lerinizi h\u0131zland\u0131r\u0131n. Bu rehber ile gereksiz y\u00fcklerden kurtulun!<\/p>\n
Her geli\u015ftirici bilir ki, modern yaz\u0131l\u0131m projeleri tek ba\u015f\u0131na yaz\u0131lmaz. Genellikle, projemize yeni \u00f6zellikler katmak, tekrarlayan g\u00f6revleri otomatikle\u015ftirmek veya karma\u015f\u0131k problemleri \u00e7\u00f6zmek i\u00e7in \u00fc\u00e7\u00fcnc\u00fc taraf k\u00fct\u00fcphanelerden ve paketlerden yararlan\u0131r\u0131z. Bu ba\u011f\u0131ml\u0131l\u0131klar, geli\u015ftirme s\u00fcrecimizi h\u0131zland\u0131r\u0131r ve bizi tekerle\u011fi yeniden icat etmekten kurtar\u0131r. Ancak, zamanla projeler geli\u015ftik\u00e7e, mimariler de\u011fi\u015fir, \u00f6zellikler eklenir ve \u00e7\u0131kar\u0131l\u0131r. Bu dinamik s\u00fcre\u00e7te, bir zamanlar kritik olan baz\u0131 ba\u011f\u0131ml\u0131l\u0131klar art\u0131k kullan\u0131lmayabilir hale gelir.<\/p>\n
Peki, bu “kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar” ne gibi sorunlara yol a\u00e7ar? \u0130lk olarak, projenizin disk \u00fczerindeki boyutunu ve dolay\u0131s\u0131yla derleme veya da\u011f\u0131t\u0131m paketinizin boyutunu gereksiz yere art\u0131r\u0131r. K\u00fc\u00e7\u00fck bir proje i\u00e7in bu fark edilmeyebilirken, b\u00fcy\u00fck \u00f6l\u00e7ekli uygulamalarda bu durum, da\u011f\u0131t\u0131m s\u00fcrelerini uzatabilir, sunucu depolama maliyetlerini art\u0131rabilir ve kullan\u0131c\u0131lar\u0131n indirme s\u00fcrelerini uzatarak k\u00f6t\u00fc bir deneyim sunabilir.<\/p>\n
\u0130kinci olarak, g\u00fcvenlik a\u00e7\u0131s\u0131ndan ciddi riskler bar\u0131nd\u0131r\u0131rlar. Kullan\u0131lmayan bir ba\u011f\u0131ml\u0131l\u0131k, projenizin kod taban\u0131nda pasif bir tehdit gibi durur. Bu k\u00fct\u00fcphanenin bilinen bir g\u00fcvenlik a\u00e7\u0131\u011f\u0131 (CVE) varsa ve siz onu g\u00fcncel tutmuyorsan\u0131z, potansiyel bir sald\u0131r\u0131 vekt\u00f6r\u00fc olu\u015fturmu\u015f olursunuz. Aktif olarak kullan\u0131lmayan bir k\u00fct\u00fcphanenin g\u00fcvenlik yamalar\u0131n\u0131 takip etmek veya g\u00fcncellemek genellikle akla gelmez, bu da riskin fark edilmeden kalmas\u0131na neden olabilir. B\u00f6ylece, projenizin genel g\u00fcvenlik duru\u015fu zay\u0131flam\u0131\u015f olur.<\/p>\n
\u00dc\u00e7\u00fcnc\u00fc olarak, bak\u0131m zorlu\u011funu art\u0131r\u0131rlar. Gereksiz ba\u011f\u0131ml\u0131l\u0131klar, Son olarak, gereksiz ba\u011f\u0131ml\u0131l\u0131klar uygulaman\u0131n ba\u015flang\u0131\u00e7 s\u00fcresini ve \u00e7al\u0131\u015fma zaman\u0131 performans\u0131n\u0131 etkileyebilir. \u00d6zellikle dinamik y\u00fcklenen veya \u00e7al\u0131\u015fma zaman\u0131nda derlenen dillerde, her bir ba\u011f\u0131ml\u0131l\u0131k belirli bir miktar kaynak t\u00fcketir. Bu ek y\u00fck, uygulaman\u0131n genel yan\u0131t s\u00fcresini ve verimlili\u011fini d\u00fc\u015f\u00fcrebilir. \u00d6zetle, kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar sadece bir “temizlik” meselesi de\u011fil, ayn\u0131 zamanda projenizin sa\u011fl\u0131\u011f\u0131, g\u00fcvenli\u011fi ve performans\u0131n\u0131 do\u011frudan etkileyen kritik bir konudur. Bu rehberde, bu g\u00f6r\u00fcnmez y\u00fcklerden nas\u0131l kurtulaca\u011f\u0131m\u0131z\u0131 ad\u0131m ad\u0131m inceleyece\u011fiz.<\/p>\n Yaz\u0131l\u0131m d\u00fcnyas\u0131nda “ba\u011f\u0131ml\u0131l\u0131k” kavram\u0131, bir projenin d\u00fczg\u00fcn \u00e7al\u0131\u015fabilmesi i\u00e7in ihtiya\u00e7 duydu\u011fu harici kod par\u00e7ac\u0131klar\u0131n\u0131 ifade eder. Bu par\u00e7ac\u0131klar, genellikle k\u00fct\u00fcphaneler, mod\u00fcller, paketler veya framework’ler \u015feklinde kar\u015f\u0131m\u0131za \u00e7\u0131kar. \u00d6rne\u011fin, bir web uygulamas\u0131nda HTTP isteklerini daha kolay yapmak i\u00e7in Axios (JavaScript), veri taban\u0131 etkile\u015fimleri i\u00e7in SQLAlchemy (Python) veya kullan\u0131c\u0131 aray\u00fcz\u00fc bile\u015fenleri i\u00e7in React (JavaScript) gibi k\u00fct\u00fcphaneleri ba\u011f\u0131ml\u0131l\u0131k olarak ekleyebiliriz. Temelde, bu ba\u011f\u0131ml\u0131l\u0131klar, biz geli\u015ftiricilerin “tekerle\u011fi yeniden icat etme” y\u00fck\u00fcnden kurtar\u0131r, DRY (Don’t Repeat Yourself) prensibini uygulamam\u0131z\u0131 sa\u011flar ve projelerimizin daha h\u0131zl\u0131 ilerlemesine olanak tan\u0131r.<\/p>\n Ba\u011f\u0131ml\u0131l\u0131klar genellikle iki ana kategoriye ayr\u0131l\u0131r: Do\u011frudan (Direct) Ba\u011f\u0131ml\u0131l\u0131klar<\/strong> ve Ge\u00e7i\u015fli (Transitive) Ba\u011f\u0131ml\u0131l\u0131klar<\/strong>. Do\u011frudan ba\u011f\u0131ml\u0131l\u0131klar, projenizin do\u011frudan kulland\u0131\u011f\u0131 ve yap\u0131land\u0131rma dosyan\u0131zda ( Ayr\u0131ca, ba\u011f\u0131ml\u0131l\u0131klar genellikle \u00dcretim Ba\u011f\u0131ml\u0131l\u0131klar\u0131 (Production Dependencies)<\/strong> ve Geli\u015ftirme Ba\u011f\u0131ml\u0131l\u0131klar\u0131 (Development Dependencies)<\/strong> olarak da ayr\u0131l\u0131r. \u00dcretim ba\u011f\u0131ml\u0131l\u0131klar\u0131, uygulaman\u0131z\u0131n canl\u0131 ortamda \u00e7al\u0131\u015fabilmesi i\u00e7in kesinlikle gerekli olanlard\u0131r. Geli\u015ftirme ba\u011f\u0131ml\u0131l\u0131klar\u0131 ise, sadece geli\u015ftirme, test, derleme veya linting gibi s\u00fcre\u00e7lerde kullan\u0131lan ve canl\u0131 ortamda ihtiya\u00e7 duyulmayan k\u00fct\u00fcphanelerdir (\u00f6rn. test framework’leri, kod formatlay\u0131c\u0131lar, derleyiciler). Bu ayr\u0131m, genellikle paket y\u00f6neticisi yap\u0131land\u0131rma dosyalar\u0131nda belirtilir ve da\u011f\u0131t\u0131m boyutunu optimize etmek i\u00e7in \u00f6nemlidir.<\/p>\n Peki, bu ba\u011f\u0131ml\u0131l\u0131klar neden “kullan\u0131lmayan” hale gelir? Birincisi, bir \u00f6zelli\u011fin veya mod\u00fcl\u00fcn projeden kald\u0131r\u0131lmas\u0131 ancak o \u00f6zelli\u011fin ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n\u0131n unutulmas\u0131yla olabilir. \u0130kincisi, bir k\u00fct\u00fcphaneden ba\u015fka bir k\u00fct\u00fcphaneye ge\u00e7i\u015f yap\u0131ld\u0131\u011f\u0131nda, eski k\u00fct\u00fcphane kald\u0131r\u0131lmay\u0131 atlanabilir. \u00dc\u00e7\u00fcnc\u00fcs\u00fc, geli\u015ftirme s\u0131ras\u0131nda deneme ama\u00e7l\u0131 eklenen ancak sonradan kullan\u0131lmayan paketler listede kalabilir. D\u00f6rd\u00fcnc\u00fcs\u00fc, b\u00fcy\u00fck ve karma\u015f\u0131k projelerde, farkl\u0131 ekiplerin farkl\u0131 ba\u011f\u0131ml\u0131l\u0131k setleri kullanmas\u0131 ve bu setlerin zamanla \u00fcst \u00fcste binmesi m\u00fcmk\u00fcnd\u00fcr. Son olarak, bazen bir k\u00fct\u00fcphane sadece k\u0131saca kullan\u0131l\u0131r ve daha sonra projenin ba\u015fka bir yerinde benzer i\u015flevi g\u00f6ren kendi kodunuz yaz\u0131l\u0131r, ancak eski k\u00fct\u00fcphane unutulur. T\u00fcm bu senaryolar, projelerimizde gereksiz bir y\u00fck olu\u015fmas\u0131na neden olur ve bu y\u00fck\u00fc d\u00fczenli olarak temizlemek, projemizin sa\u011fl\u0131\u011f\u0131 i\u00e7in hayati \u00f6neme sahiptir.<\/p>\n Kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar\u0131 bulmak, bazen dedektiflik yapmay\u0131 gerektirir. Neyse ki, bu s\u00fcre\u00e7te bize yard\u0131mc\u0131 olabilecek hem manuel hem de otomatik y\u00f6ntemler mevcut. Her iki yakla\u015f\u0131m da kendi i\u00e7inde avantajlara ve dezavantajlara sahiptir ve genellikle en iyi sonu\u00e7lar i\u00e7in birlikte kullan\u0131lmalar\u0131 \u00f6nerilir.<\/p>\n Manuel inceleme, \u00f6zellikle daha k\u00fc\u00e7\u00fck projeler i\u00e7in veya otomatik ara\u00e7lar\u0131n yetersiz kald\u0131\u011f\u0131 durumlarda olduk\u00e7a de\u011ferli bir y\u00f6ntemdir. Bu yakla\u015f\u0131m, temelde projenizin ba\u011f\u0131ml\u0131l\u0131k yap\u0131land\u0131rma dosyas\u0131n\u0131 ve kod taban\u0131n\u0131 elle g\u00f6zden ge\u00e7irmeyi i\u00e7erir. \u0130\u015fte ad\u0131m ad\u0131m nas\u0131l yap\u0131laca\u011f\u0131:<\/p>\n Bu dosyalarda listelenen her bir paketin ad\u0131n\u0131 not al\u0131n.\n <\/li>\n Manuel incelemenin zorluklar\u0131, \u00f6zellikle b\u00fcy\u00fck projelerde zaman al\u0131c\u0131 ve hataya a\u00e7\u0131k olmas\u0131d\u0131r. \u0130nsan g\u00f6z\u00fcnden ka\u00e7abilecek detaylar olabilir ve her zaman do\u011fru karar\u0131 vermek kolay de\u011fildir. Ancak, projenizin i\u00e7 yap\u0131s\u0131n\u0131 derinlemesine anlaman\u0131za yard\u0131mc\u0131 olur.<\/p>\n Otomatik ara\u00e7lar, manuel incelemenin eksikliklerini gidererek, ba\u011f\u0131ml\u0131l\u0131k tespitini \u00e7ok daha h\u0131zl\u0131 ve g\u00fcvenilir hale getirir. Her programlama ekosisteminin kendine \u00f6zg\u00fc g\u00fc\u00e7l\u00fc ara\u00e7lar\u0131 vard\u0131r:<\/p>\n \u00d6rnek Kullan\u0131m (depcheck):<\/strong><\/p>\n <\/code><\/p>\n Bu komut, projenizin k\u00f6k dizininde \u00e7al\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131nda kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar\u0131n bir listesini verecektir.<\/p>\n<\/li>\n \u00d6rnek Kullan\u0131m (pip-autoremove):<\/strong><\/p>\n <\/code><\/p>\n Bu komut, belirtilen paketi ve onun kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 kald\u0131r\u0131r.<\/p>\n<\/li>\n \u00d6rnek Kullan\u0131m (composer-unused):<\/strong><\/p>\n <\/code><\/p>\n Bu komut, projenizdeki \u00d6rnek Kullan\u0131m (Maven):<\/strong><\/p>\n <\/code><\/p>\n Bu komut, \u00e7\u0131kt\u0131 olarak \"Used undeclared dependencies\" (kullan\u0131lan ama tan\u0131mlanmam\u0131\u015f) ve \"Unused declared dependencies\" (tan\u0131mlanm\u0131\u015f ama kullan\u0131lmayan) gibi bilgiler sunar.<\/p>\n<\/li>\n<\/ul>\n Otomatik ara\u00e7lar, genellikle manuel incelemeden \u00e7ok daha h\u0131zl\u0131 ve verimli sonu\u00e7lar verir. Ancak, bazen \"false positive\" (yanl\u0131\u015f pozitif) sonu\u00e7lar verebilirler. \u00d6rne\u011fin, bir k\u00fct\u00fcphane kodda do\u011frudan \u00e7a\u011fr\u0131lmayabilir ancak bir konfig\u00fcrasyon dosyas\u0131 arac\u0131l\u0131\u011f\u0131yla veya dinamik olarak y\u00fcklenebilir. Bu gibi durumlarda, otomatik ara\u00e7lar\u0131n \u00e7\u0131kt\u0131s\u0131n\u0131 manuel olarak do\u011frulamak \u00f6nemlidir. En iyi yakla\u015f\u0131m, bu ara\u00e7lar\u0131 bir ba\u015flang\u0131\u00e7 noktas\u0131 olarak kullanmak ve ard\u0131ndan tespit edilen ba\u011f\u0131ml\u0131l\u0131klar\u0131 dikkatlice inceleyerek nihai karar\u0131 vermektir.<\/p>\n \u015eimdi, \u00f6\u011frendiklerimizi ger\u00e7ek bir senaryo \u00fczerinde uygulayal\u0131m. Orta \u00f6l\u00e7ekli bir Node.js tabanl\u0131 web uygulamas\u0131n\u0131 (\u00f6rne\u011fin, eski bir Express.js projesi) ele alal\u0131m. Zamanla, bu projede \u00e7e\u015fitli \u00f6zellikler eklenip \u00e7\u0131kar\u0131lm\u0131\u015f, baz\u0131 ba\u011f\u0131ml\u0131l\u0131klar g\u00fcncellenmi\u015f ancak eskileri unutulmu\u015f durumda. Amac\u0131m\u0131z, projeyi gereksiz y\u00fcklerden ar\u0131nd\u0131rmak ve daha temiz bir kod taban\u0131 elde etmek.<\/p>\n \u00d6ncelikle, projenizin bulundu\u011fu dizine gidin ve mevcut ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131z\u0131 listeleyin. Bu, projenizin ba\u015flang\u0131\u00e7 durumu hakk\u0131nda bir fikir edinmenizi sa\u011flayacakt\u0131r.<\/p>\n <\/code><\/p>\n <\/code><\/p>\n Bu listeye bakarak, projemizde \u015eimdi, otomatik bir ara\u00e7 olan <\/code><\/p>\n Kurulum tamamland\u0131ktan sonra, projenizin k\u00f6k dizininde <\/code><\/p>\n Komutun \u00e7\u0131kt\u0131s\u0131 \u015f\u00f6yle bir \u015fey olabilir:<\/p>\n <\/code><\/p>\n Bu \u00e7\u0131kt\u0131 bize, package.json<\/code>, requirements.txt<\/code> veya pom.xml<\/code> gibi yap\u0131land\u0131rma dosyalar\u0131n\u0131 kalabal\u0131kla\u015ft\u0131r\u0131r. Bu durum, yeni geli\u015ftiricilerin projeye adaptasyonunu zorla\u015ft\u0131rabilir, hangi k\u00fct\u00fcphanelerin ger\u00e7ekten gerekli oldu\u011funu anlamalar\u0131n\u0131 g\u00fc\u00e7le\u015ftirebilir. Ayr\u0131ca, ba\u011f\u0131ml\u0131l\u0131k \u00e7ak\u0131\u015fmalar\u0131 veya versiyon uyu\u015fmazl\u0131klar\u0131 gibi sorunlar ortaya \u00e7\u0131kt\u0131\u011f\u0131nda, sorunun kayna\u011f\u0131n\u0131 bulmak daha karma\u015f\u0131k hale gelir \u00e7\u00fcnk\u00fc gereksiz ba\u011f\u0131ml\u0131l\u0131klar da potansiyel su\u00e7lu listesinde yer al\u0131r.<\/p>\nBa\u011f\u0131ml\u0131l\u0131k Y\u00f6netimi 101: Temel Kavramlar\u0131 Anlayal\u0131m m\u0131?<\/h2>\n
package.json<\/code>, requirements.txt<\/code>, composer.json<\/code> vb.) a\u00e7\u0131k\u00e7a belirtti\u011finiz k\u00fct\u00fcphanelerdir. \u00d6rne\u011fin, bir Node.js projesinde Express.js kullan\u0131yorsan\u0131z, bu do\u011frudan bir ba\u011f\u0131ml\u0131l\u0131kt\u0131r. Ge\u00e7i\u015fli ba\u011f\u0131ml\u0131l\u0131klar ise, do\u011frudan ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131z\u0131n ihtiya\u00e7 duydu\u011fu di\u011fer k\u00fct\u00fcphanelerdir. Siz bunlar\u0131 do\u011frudan belirtmezsiniz, ancak paket y\u00f6neticisi (npm, pip, composer vb.) bunlar\u0131 otomatik olarak indirir ve kurar. \u00d6rne\u011fin, Express.js’in alt\u0131nda \u00e7al\u0131\u015fan bir ba\u015fka k\u00fct\u00fcphane, sizin projeniz i\u00e7in ge\u00e7i\u015fli bir ba\u011f\u0131ml\u0131l\u0131kt\u0131r.<\/p>\nKullan\u0131lmayan Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Tespit Etmenin Temel Y\u00f6ntemleri Nelerdir?<\/h2>\n
Manuel \u0130nceleme: G\u00f6zden Ka\u00e7anlar\u0131 Yakalama Sanat\u0131 Nas\u0131l Geli\u015ftirilir?<\/h3>\n
\n
\n
package.json<\/code> dosyas\u0131ndaki dependencies<\/code> ve devDependencies<\/code> b\u00f6l\u00fcmlerini kontrol edin.<\/li>\nrequirements.txt<\/code> veya pyproject.toml<\/code> (Poetry, PDM) dosyalar\u0131n\u0131 g\u00f6zden ge\u00e7irin.<\/li>\ncomposer.json<\/code> dosyas\u0131ndaki require<\/code> ve require-dev<\/code> b\u00f6l\u00fcmlerine bak\u0131n.<\/li>\npom.xml<\/code> dosyas\u0131ndaki Gemfile<\/code> dosyas\u0131n\u0131 kontrol edin.<\/li>\n<\/ul>\ngrep<\/code>) bu t\u00fcr aramalar\u0131 kolayca yapman\u0131za olanak tan\u0131r.\n\n
import React from 'react';<\/code> veya require('lodash');<\/code> gibi ifadeler aray\u0131n.<\/li>\nimport requests<\/code> veya from flask import Flask<\/code> gibi ifadeler aray\u0131n.<\/li>\nuse Symfony\\Component\\Console\\Command\\Command;<\/code> gibi ifadeler aray\u0131n.<\/li>\nimport org.springframework.boot.SpringApplication;<\/code> gibi ifadeler aray\u0131n.<\/li>\n<\/ul>\n<\/li>\nimport<\/code> edilmez ancak bir konfig\u00fcrasyon dosyas\u0131 (\u00f6rne\u011fin, Webpack config, Babel config) taraf\u0131ndan kullan\u0131l\u0131r. Bu durumlar\u0131 da g\u00f6z \u00f6n\u00fcnde bulundurmal\u0131s\u0131n\u0131z. Bir paket do\u011frudan \u00e7a\u011fr\u0131lmasa bile, bir framework veya ba\u015fka bir ba\u011f\u0131ml\u0131l\u0131k taraf\u0131ndan dahili olarak kullan\u0131l\u0131yor olabilir.<\/li>\n<\/ol>\nOtomatik Ara\u00e7lar: Paket Y\u00f6neticilerinin G\u00fcc\u00fcnden Nas\u0131l Yararlan\u0131l\u0131r?<\/h3>\n
\n
\n
depcheck<\/code>: Bu ara\u00e7, package.json<\/code> dosyan\u0131zdaki ba\u011f\u0131ml\u0131l\u0131klar\u0131 analiz eder ve kod taban\u0131n\u0131zda kullan\u0131lmayanlar\u0131 veya eksik olanlar\u0131 bildirir.<\/li>\nnpm-check<\/code>: Ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131z\u0131n g\u00fcncel olup olmad\u0131\u011f\u0131n\u0131, kullan\u0131lmayanlar\u0131 ve hatal\u0131 olanlar\u0131 interaktif bir \u015fekilde kontrol etmenizi sa\u011flar.<\/li>\n<\/ul>\n\nnpm install -g depcheck\ndepcheck\n <\/pre>\n\n
pip-autoremove<\/code>: Bu ara\u00e7, bir paketi kald\u0131rd\u0131\u011f\u0131n\u0131zda onunla birlikte gelen ge\u00e7i\u015fli ba\u011f\u0131ml\u0131l\u0131klar\u0131 da otomatik olarak kald\u0131r\u0131r. Ancak tespit i\u00e7in do\u011frudan bir ara\u00e7 de\u011fildir.<\/li>\npigar<\/code>: Python projenizdeki import ifadelerinden requirements.txt<\/code> dosyas\u0131n\u0131 otomatik olarak olu\u015fturmaya \u00e7al\u0131\u015f\u0131r. Mevcut requirements.txt<\/code> ile kar\u015f\u0131la\u015ft\u0131r\u0131larak kullan\u0131lmayanlar bulunabilir.<\/li>\nvulture<\/code>: Kullan\u0131lmayan Python kodunu bulan bir ara\u00e7t\u0131r, ba\u011f\u0131ml\u0131l\u0131klar\u0131 do\u011frudan listelemez ancak kodunuzdaki \u00f6l\u00fc ba\u011f\u0131ml\u0131l\u0131k kullan\u0131mlar\u0131n\u0131 bulmaya yard\u0131mc\u0131 olabilir.<\/li>\n<\/ul>\n\npip install pip-autoremove\npip-autoremove \n
php-tui\/composer-unused<\/code>: Composer tabanl\u0131 projelerde kullan\u0131lmayan ba\u011f\u0131ml\u0131l\u0131klar\u0131 tespit etmek i\u00e7in tasarlanm\u0131\u015f \u00f6zel bir ara\u00e7t\u0131r.<\/li>\n<\/ul>\n\ncomposer global require 'php-tui\/composer-unused'\ncomposer unused\n <\/pre>\ncomposer.json<\/code>'\u0131 ve kod taban\u0131n\u0131z\u0131 analiz ederek kullan\u0131lmayan paketleri listeler.<\/p>\n<\/li>\n\n
mvn dependency:analyze<\/code>: Maven'\u0131n kendi ba\u011f\u0131ml\u0131l\u0131k analizi arac\u0131d\u0131r. Projenizdeki pom.xml<\/code> dosyas\u0131n\u0131 inceler ve kullan\u0131lmayan do\u011frudan ba\u011f\u0131ml\u0131l\u0131klar\u0131 veya eksik olanlar\u0131 tespit etmeye \u00e7al\u0131\u015f\u0131r.<\/li>\n<\/ul>\n\nmvn dependency:analyze\n <\/pre>\nPratik Uygulama: Node.js Projesinde Kullan\u0131lmayan Ba\u011f\u0131ml\u0131l\u0131k Temizli\u011fi (Vaka Analizi)<\/h2>\n
Ad\u0131m 1: Projeyi Haz\u0131rlama ve Mevcut Durumu G\u00f6zden Ge\u00e7irme<\/h3>\n
\ncd \/yol\/to\/your\/node-project\nls -l node_modules\/ # veya do\u011frudan package.json dosyas\u0131n\u0131 a\u00e7\u0131n\n<\/pre>\npackage.json<\/code> dosyan\u0131z\u0131 a\u00e7t\u0131\u011f\u0131n\u0131zda, dependencies<\/code> ve devDependencies<\/code> b\u00f6l\u00fcmlerinde bir dizi paketin listelendi\u011fini g\u00f6receksiniz. \u00d6rne\u011fin:<\/p>\n\n{\n \"name\": \"my-old-web-app\",\n \"version\": \"1.0.0\",\n \"dependencies\": {\n \"express\": \"^4.17.1\",\n \"mongoose\": \"^5.12.3\",\n \"body-parser\": \"^1.19.0\",\n \"lodash\": \"^4.17.21\",\n \"axios\": \"^0.21.1\",\n \"moment\": \"^2.29.1\",\n \"debug\": \"^4.3.1\",\n \"unused-package-example\": \"^1.0.0\" \/\/ Bu paket sadece deneme ama\u00e7l\u0131 eklenmi\u015fti\n },\n \"devDependencies\": {\n \"nodemon\": \"^2.0.7\",\n \"eslint\": \"^7.23.0\",\n \"mocha\": \"^8.3.2\",\n \"chai\": \"^4.3.4\",\n \"unnecessary-dev-tool\": \"^1.0.0\" \/\/ Bu da deneme ama\u00e7l\u0131 eklendi\n }\n}\n<\/pre>\nunused-package-example<\/code> ve unnecessary-dev-tool<\/code> ad\u0131nda iki \u015f\u00fcpheli ba\u011f\u0131ml\u0131l\u0131k oldu\u011funu varsayal\u0131m.<\/p>\nAd\u0131m 2:
depcheck<\/code> Kurulumu ve Kullan\u0131m\u0131<\/h3>\ndepcheck<\/code>'i kullanarak bu \u015f\u00fcpheli ba\u011f\u0131ml\u0131l\u0131klar\u0131 tespit edelim. depcheck<\/code>'i global olarak veya projenizin devDependencies<\/code>'\u0131na ekleyerek kullanabilirsiniz.<\/p>\n\nnpm install -g depcheck # Global kurulum (tercih edilir)\n# veya\nnpm install depcheck --save-dev # Proje baz\u0131nda kurulum\n<\/pre>\ndepcheck<\/code> komutunu \u00e7al\u0131\u015ft\u0131r\u0131n:<\/p>\n\ndepcheck\n<\/pre>\n\nUnused dependencies\n* unused-package-example\n* moment (Moment.js, projede art\u0131k tarih i\u015flemleri i\u00e7in native Date objeleri kullan\u0131l\u0131yor olabilir.)\n\nUnused devDependencies\n* unnecessary-dev-tool\n\nMissing dependencies\n(Hi\u00e7bir eksik ba\u011f\u0131ml\u0131l\u0131k bulunamad\u0131.)\n<\/pre>\nunused-package-example<\/code> ve moment<\/code>'in \u00fcretim ba\u011f\u0131ml\u0131l\u0131klar\u0131 aras\u0131nda, unnecessary-dev-tool<\/code>'un ise geli\u015ftirme ba\u011f\u0131ml\u0131l\u0131klar\u0131 aras\u0131nda kullan\u0131lmad\u0131\u011f\u0131n\u0131 g\u00f6steriyor.<\/p>\nAd\u0131m 3: Tespit Edilen Ba\u011f\u0131ml\u0131l\u0131klar\u0131 Analiz Etme (False Positives)<\/h3>\n
depcheck<\/code> gibi ara\u00e7lar olduk\u00e7a etkilidir, ancak bazen \"yanl\u0131\u015f pozitif\" (false positive) sonu\u00e7lar verebilirler. \u00d6rne\u011fin:<\/p>\n\n
import<\/code> edilmese de, bir konfig\u00fcrasyon dosyas\u0131 (\u00f6rn. Webpack, Babel) taraf\u0131ndan dinamik olarak y\u00fckleniyor olabilir.<\/li>\nexpress-generator<\/code> gibi bir iskelet olu\u015fturucu).<\/li>\n