<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by cengiz ilhan on Medium]]></title>
        <description><![CDATA[Stories by cengiz ilhan on Medium]]></description>
        <link>https://medium.com/@cngzilhn?source=rss-307d7cd2a953------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nqVoYTA9sEVSVtttoUwGbg.png</url>
            <title>Stories by cengiz ilhan on Medium</title>
            <link>https://medium.com/@cngzilhn?source=rss-307d7cd2a953------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:55:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cngzilhn/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Yayınladığım npm Paketleri: Z Raporu]]></title>
            <link>https://medium.com/@cngzilhn/yay%C4%B1nlad%C4%B1%C4%9F%C4%B1m-npm-paketleri-z-raporu-af4f24d11b2b?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/af4f24d11b2b</guid>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Mon, 07 Sep 2026 06:21:00 GMT</pubDate>
            <atom:updated>2026-09-08T08:28:50.810Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/710/1*ZBMgT0Icb8iMImVUV_kIKA.png" /><figcaption><a href="https://npm-stat.com/charts.html?author=sawacrow&amp;from=2023-01-01&amp;to=2026-10-10">https://npm-stat.com/charts.html?author=sawacrow&amp;from=2023-01-01&amp;to=2026-10-10</a></figcaption></figure><p>Son 3 yılda npm’de yayınladığım 8 adet paket mevcut ve toplam indirme sayıları şu an için 7200+’a ulaştı. Yıllar içinde yayınladığım npm paketlerini inceleyelim.</p><h3>Genel Bakış:</h3><p>2024 yılında yayınladığım webpack-concatjs-plugin bugüne kadar 1.400 indirmeye ulaşırken, yalnızca geçtiğimiz ay yayınladığım container-query-picture şimdiden 1.855 indirme aldı.</p><p>İki paket arasında bu kadar kısa sürede oluşan farkı yorumlamaya çalışalım. Aynı zamanda her paketin ortaya çıkış hikâyesine, hangi ihtiyacı karşılamak için geliştirildiğine ve bu ihtiyacı nasıl çözmeye çalıştığıma da kısaca değineceğim.</p><h3>container-query-picture</h3><p>HTML’deki responsive görseller için kullanılan &lt;picture&gt; elementi, görsel kaynağını seçerken container genişliğini değil, viewport/cihaz genişliğini referans alıyordu. Container genişliğini referans alarak görsel seçimi yapabileceğim bir yapı olmadığı için bu pakete ihtiyaç duydum.</p><p>Url: <a href="https://www.npmjs.com/package/container-query-picture">https://www.npmjs.com/package/container-query-picture</a></p><h3>js-global-error-handler</h3><p>JavaScript tarafındaki console ve diğer client-side hataları tek bir noktadan yakalayıp loglayabilmek için oluşturuldu.</p><p>Url: <a href="https://www.npmjs.com/package/js-global-error-handler">https://www.npmjs.com/package/js-global-error-handler</a></p><h3>webpack-concatjs-plugin</h3><p>Gulp ile oluşturulmuş legacy projeleri Webpack’e dönüştürürken bazı JavaScript dosyalarında scope ve ES module kaynaklı sorunlarla karşılaşıyordum. Bu sorunları aşmak için geliştirildi.</p><p>Url: <a href="https://www.npmjs.com/package/webpack-concatjs-plugin">https://www.npmjs.com/package/webpack-concatjs-plugin</a></p><h3>css-reference-finder</h3><p>Belirli bir dosya uzantısına sahip dosyalarda, örneğin tüm .cshtml dosyalarında çağrılan CSS dosyalarını ve bu CSS&#39;lerin çağrıldığı dosyaları listeleyen bir paket.</p><p>Projeleri refaktör ederken tekrarlı kullanımları tespit edebilmek amacıyla geliştirildi.</p><p>Url: <a href="https://www.npmjs.com/package/css-reference-finder">https://www.npmjs.com/package/css-reference-finder</a></p><h3>copy-paste-detector-js</h3><p>Legacy projeleri refaktör ederken kolaylık sağlayan bir diğer paket.</p><p>JavaScript dosyalarındaki aynı class ve method isimlerini listeleyerek tekrarlı kullanımları tespit etmeye yardımcı oluyor. Module altyapısı olmayan JavaScript projelerinde import/export kullanılamadığı için aynı method farklı dosyalara kopyalanabiliyor.</p><p>Url: <a href="https://www.npmjs.com/package/copy-paste-detector-js">https://www.npmjs.com/package/copy-paste-detector-js</a></p><h3>webpack-error2json</h3><p>Webpack’teki console hatalarını .json dosyasına yazan bir script.</p><p>Webpack dönüşüm projelerinde 999+ hata oluştuğunda console’u takip etmek ve yönetmek zorlaştığı için geliştirildi.</p><p>Url: <a href="https://www.npmjs.com/package/webpack-error2json">https://www.npmjs.com/package/webpack-error2json</a></p><h3>gsap-helper</h3><p>GSAP.js bir 2D animasyon kütüphanesidir. Sık kullandığım methodları daha basit şekilde kullanabilmek için oluşturduğum bir npm scripti oldu.</p><p>Url: <a href="https://www.npmjs.com/package/gsap-helper">https://www.npmjs.com/package/gsap-helper</a></p><h3>scss-mapper</h3><p>SCSS dosyalarını tarayıp aralarındaki bağlantı şemasını JSON formatında çıkaran, proje refaktörlerinde yardımcı olan bir script.</p><p>Url: <a href="https://www.npmjs.com/package/scss-mapper">https://www.npmjs.com/package/scss-mapper</a></p><h3><strong>İndirme Farkları</strong></h3><p><strong>webpack-concatjs-plugin</strong> ve benzeri refaktör araçları, daha çok projelerin dönüşüm veya oluşturulma aşamasında kullanılan, mimariyi belirlerken bir kez eklenen tool’lardır. Ayrıca bu tür araçlara her projede ihtiyaç duyulmayabilir.</p><p><strong>container-query-picture</strong> ise projenin altyapısından veya türünden bağımsız olarak kullanılabilecek, özellikle landing page’lerde ihtiyaç duyulabilecek bir script. Bu nedenle çok daha geniş bir kullanım alanına sahip olduğunu ve kısa sürede yüksek indirme sayısına ulaşmasının temel sebebinin bu olduğunu düşünüyorum.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=af4f24d11b2b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The npm Packages I’ve Published]]></title>
            <link>https://javascript.plainenglish.io/the-npm-packages-ive-published-34807942ea43?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/34807942ea43</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Fri, 04 Sep 2026 17:27:50 GMT</pubDate>
            <atom:updated>2026-09-04T17:27:50.485Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the past 3 years, I’ve published 8 packages on npm, with more than 7,200 total downloads so far. Let’s take a look at the npm packages I’ve published over the years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*ZBMgT0Icb8iMImVUV_kIKA.png" /><figcaption><a href="https://npm-stat.com/charts.html?author=sawacrow&amp;from=2023-01-01&amp;to=2026-10-10">https://npm-stat.com/charts.html?author=sawacrow&amp;from=2023-01-01&amp;to=2026-10-10</a></figcaption></figure><h3>Overview</h3><p>While <strong>webpack-concatjs-plugin</strong>, which I published in 2024, has reached 1,400 downloads so far, <strong>container-query-picture</strong>, which I published just last month, has already reached 1,855 downloads.</p><p>Let’s try to understand the reason behind this difference despite the relatively short period of time. I’ll also briefly talk about the story behind each package, what need led me to develop it, and how I tried to solve that problem.</p><h3>container-query-picture</h3><p>The &lt;picture&gt; element, which is used for responsive images in HTML, referenced the viewport/device width rather than the container width when selecting an image source. Since there was no built-in way to select an image source based on the container width, I needed a solution for this problem.</p><p>URL: <a href="https://www.npmjs.com/package/container-query-picture">https://www.npmjs.com/package/container-query-picture</a></p><h3>js-global-error-handler</h3><p>I created this package to capture console and other client-side JavaScript errors from a single point and log them.</p><p>URL: <a href="https://www.npmjs.com/package/js-global-error-handler">https://www.npmjs.com/package/js-global-error-handler</a></p><h3>webpack-concatjs-plugin</h3><p>While migrating legacy projects built with Gulp to Webpack, I encountered scope and ES module-related issues with some JavaScript files. I developed this package to overcome those problems.</p><p>URL: <a href="https://www.npmjs.com/package/webpack-concatjs-plugin">https://www.npmjs.com/package/webpack-concatjs-plugin</a></p><h3>css-reference-finder</h3><p>A package that scans files with a specific extension — for example, all .cshtml files — and lists the CSS files referenced in them along with the files where those CSS files are referenced.</p><p>I built it to help identify repeated usage during project refactoring.</p><p>URL: <a href="https://www.npmjs.com/package/css-reference-finder">https://www.npmjs.com/package/css-reference-finder</a></p><h3>copy-paste-detector-js</h3><p>Another package that makes refactoring legacy projects easier.</p><p>It lists identical class and method names across JavaScript files to help identify repeated usage. In JavaScript projects without a module system, import/export cannot be used, so the same method can end up being copied across different files.</p><p>URL: <a href="https://www.npmjs.com/package/copy-paste-detector-js">https://www.npmjs.com/package/copy-paste-detector-js</a></p><h3>webpack-error2json</h3><p>A script that writes Webpack console errors to a .json file.</p><p>It was created because, during Webpack migration projects, dealing with the console becomes difficult when there are 999+ errors.</p><p>URL: <a href="https://www.npmjs.com/package/webpack-error2json">https://www.npmjs.com/package/webpack-error2json</a></p><h3>gsap-helper</h3><p>GSAP.js is a 2D animation library. I created gsap-helper as an npm package to make some of the methods I frequently use easier to work with.</p><p>URL: <a href="https://www.npmjs.com/package/gsap-helper">https://www.npmjs.com/package/gsap-helper</a></p><h3>scss-mapper</h3><p>A script that scans SCSS files and generates their dependency structure in JSON format, serving as a helper for project refactoring.</p><p>URL: <a href="https://www.npmjs.com/package/scss-mapper">https://www.npmjs.com/package/scss-mapper</a></p><h3>Download Differences</h3><p><strong>webpack-concatjs-plugin</strong> and similar refactoring tools are mainly used during the migration or initial setup stages of a project. They are typically added once while defining the project architecture, and they may not be needed for every project.</p><p><strong>container-query-picture</strong>, on the other hand, can be used regardless of the project’s underlying architecture or type, and is likely to be useful on almost any landing page. Because of this, I think it has a much broader range of use cases, which is the main reason it reached a high number of downloads in such a short period of time.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34807942ea43" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/the-npm-packages-ive-published-34807942ea43">The npm Packages I’ve Published</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Platform Notes #001 — Container Queries Support for <picture>]]></title>
            <link>https://javascript.plainenglish.io/web-platform-notes-001-container-queries-support-for-picture-ac3735bae906?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac3735bae906</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 13:43:30 GMT</pubDate>
            <atom:updated>2026-08-09T15:08:57.214Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is the problem?</h3><p>When we use responsive images, we usually use the &lt;picture&gt; element:</p><pre>&lt;picture&gt;<br>  &lt;source media=&quot;(min-width: 650px)&quot; srcset=&quot;large.jpg&quot;&gt;<br>  &lt;source media=&quot;(min-width: 465px)&quot; srcset=&quot;medium.jpg&quot;&gt;<br>  &lt;img src=&quot;small.jpg&quot; alt=&quot;Flowers&quot;&gt;<br>&lt;/picture&gt;</pre><p>The problem is that the media queries in &lt;source&gt; use the viewport width as a reference.</p><p>We can select different images for mobile and desktop, but we cannot use the container or component width as a reference. So, we cannot select the image based on the container size.</p><p>For example, on a 1440px screen, an image inside a 300px sidebar and an image inside a 900px content area will use the same viewport media queries.</p><h3>Possible Solution</h3><p>The &lt;picture&gt; HTML element needs to be able to query the container width.</p><p>There have been a few proposals and discussions about this in WHATWG.</p><p><strong>Issue 1:</strong></p><p><a href="https://github.com/whatwg/html/issues/10182">Allow </a><a href="https://github.com/whatwg/html/issues/10182">&lt;source&gt; elements to query container sizes · Issue #10182 · whatwg/html</a></p><p>The basic idea here is adding something like a container attribute to the &lt;source&gt; element.</p><pre>&lt;picture&gt;<br>  &lt;source srcset=&quot;image-wide.png&quot; container=&quot;(width &gt; 800px)&quot;&gt;<br>  &lt;source srcset=&quot;image-medium.png&quot; container=&quot;(width &gt; 600px)&quot;&gt;<br>  &lt;img src=&quot;image-narrow.png&quot; alt=&quot;&quot;&gt;<br>&lt;/picture&gt;</pre><p>But there are some problems with this approach.</p><p>As myakura mentioned, the browser would need to wait for the layout to be calculated in order to know the container size. This can cause some performance problems because images can normally start loading as early as possible.</p><p><strong>Issue 2:</strong></p><p><a href="https://github.com/w3c/csswg-drafts/issues/5889">Container Queries for Images · CSSWG #5889</a></p><p>Preloading, performance and art direction are also discussed in this issue.</p><p>So, what looks like a simple feature — “let’s query the container width as well” — actually creates some problems for the browser’s image loading process.</p><p>There seem to be some blockers in the current approach, but especially with grid, masonry and component-based layouts, I think there is a real need for this feature.</p><p>After all, an image usually fills a container, not the screen itself.</p><p>It is not in the implementation stage for now, but I wouldn’t be surprised if we see &lt;picture&gt; support for container queries in the future.</p><p><strong>To solve this problem with npm:</strong><br> <a href="https://www.npmjs.com/package/container-query-picture">container-query-picture · npm</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac3735bae906" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/web-platform-notes-001-container-queries-support-for-picture-ac3735bae906">Web Platform Notes #001 — Container Queries Support for &lt;picture&gt;</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Platform Notları #001 — <picture> için Container Queries Desteği]]></title>
            <link>https://medium.com/@cngzilhn/web-platform-notlar%C4%B1-001-picture-i%C3%A7in-container-queries-deste%C4%9Fi-a2a040118696?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2a040118696</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Sun, 09 Aug 2026 13:42:26 GMT</pubDate>
            <atom:updated>2026-08-09T15:07:41.286Z</atom:updated>
            <content:encoded><![CDATA[<h3>Sorun nedir?</h3><p>Mevcutta responsive image kullandığımızda genellikle &lt;picture&gt; kullanıyoruz:</p><pre>&lt;picture&gt;<br>  &lt;source media=&quot;(min-width: 650px)&quot; srcset=&quot;large.jpg&quot;&gt;<br>  &lt;source media=&quot;(min-width: 465px)&quot; srcset=&quot;medium.jpg&quot;&gt;<br>  &lt;img src=&quot;small.jpg&quot; alt=&quot;Flowers&quot;&gt;<br>&lt;/picture&gt;</pre><p>Sorun şu ki source media sorguları viewport genişliğini referans alır. Mobil-desktop seçebilirsiniz ama container-component width’i referans almaz. Dolayısıyla container’a göre seçim yapamayız.</p><p>Örneğin 1440px’lik bir ekranda 300px’lik bir sidebar içerisinde bulunan image ile 900px’lik content alanında bulunan image için aynı viewport sorguları çalışıyor.</p><h3>Çözüm Yolu</h3><p>&lt;picture&gt; html elementinin container width&#39;i query edebilmesi gerekiyor. Bu konuda WHATWG&#39;de birkaç talep açılıp tartışılmış.</p><p><strong>Issue 1:</strong></p><p><a href="https://github.com/whatwg/html/issues/10182">Allow </a><a href="https://github.com/whatwg/html/issues/10182">&lt;source&gt; elements to query container sizes · Issue #10182 · whatwg/html</a></p><p>Burada önerilen şey kabaca &lt;source&gt; elementine container gibi bir attribute eklenmesi.</p><pre>&lt;picture&gt;<br>  &lt;source srcset=&quot;image-wide.png&quot; container=&quot;(width &gt; 800px)&quot;&gt;<br>  &lt;source srcset=&quot;image-medium.png&quot; container=&quot;(width &gt; 600px)&quot;&gt;<br>  &lt;img src=&quot;image-narrow.png&quot; alt=&quot;&quot;&gt;<br>&lt;/picture&gt;</pre><p>Ama burada bazı problemler var. myakura’nın bahsettiği gibi bunun gerçekleşebilmesi için layout’un render edilmesinin beklenmesi gerekiyor. Bu da image’ın mümkün olduğunca erken yüklenmesi tarafında bazı performans problemleri oluşturabilir.</p><p><strong>Issue 2:</strong></p><p><a href="https://github.com/w3c/csswg-drafts/issues/5889">Container Queries for Images · CSSWG #5889</a></p><p>Buradaki tartışmalarda da preload, performans ve art direction gibi konular konuşulmuş.</p><p>Yani ilk bakışta “container width’i de query edelim” gibi basit görünen bir özellik aslında browser’ın image loading tarafında bazı problemler oluşturuyor.</p><p>Mevcut yapıda engeller var gibi görünüyor ama özellikle grid, masonry ve component bazlı yapılarda image’ın çoğu zaman ekranı değil bir container’ı doldurduğunu düşünürsek bence böyle bir özelliğe ihtiyaç var.</p><p>Şu an için implementasyon aşamasında değil ama ileride böyle bir &lt;picture&gt; desteği gelirse şaşırmayız.</p><p><strong>Sorunu npm ile çözmek için:</strong><br><a href="https://www.npmjs.com/package/container-query-picture"> container-query-picture · npm</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2a040118696" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Make Unresponsive iFrames and Ads Responsive with CSS Transform]]></title>
            <link>https://javascript.plainenglish.io/how-to-make-unresponsive-iframes-and-ads-responsive-with-css-transform-e4a6508077fa?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/e4a6508077fa</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[advertising]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 09:17:19 GMT</pubDate>
            <atom:updated>2026-08-07T11:30:47.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/463/1*Wov8VzEPMtzkpOivYHXaKw.png" /></figure><p>Third-party embeds — ad tags, iframes, widgets — come with hardcoded width and height attributes you can’t override. CSS width: 100% won’t help — the embed ignores it. The fix: measure the parent container’s width, divide by the embed’s fixed width to get a scale ratio, then apply it via transform: scale(). Since transform is purely visual and doesn’t affect layout, the parent’s height must also be corrected manually to prevent overflow.</p><pre>&lt;!DOCTYPE html&gt;<br>&lt;html lang=&quot;en&quot;&gt;<br>  &lt;head&gt;<br>    &lt;meta charset=&quot;UTF-8&quot;&gt;<br>    &lt;link rel=&quot;stylesheet&quot; href=&quot;./style.css&quot;&gt;<br>    &lt;meta name=&quot;viewport&quot; content=&quot;width=device-width, initial-scale=1.0&quot;&gt;<br>    &lt;title&gt;Pen&lt;/title&gt;<br>  &lt;/head&gt;<br>  &lt;body&gt;<br>        &lt;div&gt;<br>        &lt;h1&gt; How to Make Unresponsive iFrames and Ads Responsive with CSS Transform&lt;/h1&gt;<br>        &lt;p&gt;Third-party embeds — ad tags, iframes, widgets — come with hardcoded width and height attributes you can&#39;t<br>            override. CSS width: 100% won&#39;t help — the embed ignores it. The fix: measure the parent container&#39;s width,<br>            divide by the embed&#39;s fixed width to get a scale ratio, then apply it via transform: scale(). Since<br>            transform<br>            is purely visual and doesn&#39;t affect layout, the parent&#39;s height must also be corrected manually to prevent<br>            overflow.&lt;/p&gt;<br>    &lt;/div&gt;<br>    &lt;div class=&quot;container&quot;&gt;<br>        &lt;div class=&quot;fixed-embed d-center&quot; width=&quot;300&quot; height=&quot;250&quot;&gt;<br>            &lt;span&gt;300x250&lt;/span&gt;<br>        &lt;/div&gt;<br>    &lt;/div&gt;<br><br>    &lt;div class=&quot;container&quot;&gt;<br>        &lt;div class=&quot;fixed-embed d-center&quot; width=&quot;900&quot; height=&quot;600&quot;&gt;<br>            &lt;span&gt;900x600&lt;/span&gt;<br>        &lt;/div&gt;<br>    &lt;/div&gt;<br><br>    &lt;script src=&quot;./script.js&quot;&gt;&lt;/script&gt;<br>  &lt;/body&gt;<br>&lt;/html&gt;</pre><pre>   .container {<br>        margin-bottom: 20px;<br>    }<br><br>    .fixed-embed {<br>        border: 2px solid black;<br>        background: gray;<br>        text-align: center;<br>    }<br><br>    span {<br>        font-size: 25px;<br>        font-weight: bolder;<br>    }<br><br>    .d-center {<br>        display: flex;<br>        justify-content: center;<br>        align-items: center;<br>    }</pre><pre>    document.addEventListener(&quot;DOMContentLoaded&quot;, () =&gt; {<br>        scaleFixedEmbed()<br>        bodyResponsiveSimulator()<br>    }<br>    );<br>    window.addEventListener(&quot;resize&quot;, () =&gt; scaleFixedEmbed());<br><br>    function scaleFixedEmbed() {<br>        const embeds = document.querySelectorAll(&#39;.fixed-embed&#39;);<br>        if (!embeds.length) return;<br><br>        embeds.forEach(embed =&gt; {<br>            const parent = embed.parentElement;<br>            if (!parent) return;<br><br>            const embedW = parseInt(embed.getAttribute(&#39;width&#39;));<br>            const embedH = parseInt(embed.getAttribute(&#39;height&#39;));<br>            if (!embedW || !embedH) return;<br>            const scale = parent.offsetWidth / embedW;<br><br>            embed.style.width = embedW + &#39;px&#39;;<br>            embed.style.height = embedH + &#39;px&#39;;<br>            embed.style.transformOrigin = &#39;top left&#39;;<br>            embed.style.transform = `scale(${scale})`;<br>            parent.style.height = (embedH * scale) + &#39;px&#39;;<br>            embed.setAttribute(&#39;data-scale-fixed&#39;, &#39;true&#39;);<br>        });<br>    }<br><br>    function bodyResponsiveSimulator() {<br>        const container = document.querySelector(&#39;.container&#39;);<br><br>        setTimeout(() =&gt; {<br>            container.style.width = &#39;250px&#39;;<br>            window.dispatchEvent(new Event(&#39;resize&#39;));<br>        }, 2000);<br>        setTimeout(() =&gt; {<br>            container.style.width = &#39;600px&#39;;<br>            window.dispatchEvent(new Event(&#39;resize&#39;));<br>        }, 4000);<br>        setTimeout(() =&gt; {<br>            container.style.width = &#39;250px&#39;;<br>            window.dispatchEvent(new Event(&#39;resize&#39;));<br>        }, 6000);<br>    }</pre><p>Codepen Example:</p><p><a href="https://codepen.io/editor/cengizilhan/pen/019dcf92-ba83-79dd-af1c-8c342972ba61">How to Make Unresponsive iFrames and Ads Responsive with CSS Transform</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4a6508077fa" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/how-to-make-unresponsive-iframes-and-ads-responsive-with-css-transform-e4a6508077fa">How to Make Unresponsive iFrames and Ads Responsive with CSS Transform</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[During Git Pull: Uncommitted Changes Problem and Solution]]></title>
            <link>https://javascript.plainenglish.io/during-git-pull-uncommitted-changes-problem-and-solution-7653904732e1?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/7653904732e1</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[git]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 11:28:21 GMT</pubDate>
            <atom:updated>2026-04-29T02:18:50.169Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/354/0*ymMkbVI2ULKLA9Hw.jpg" /></figure><p>When you run <strong>“git pull”</strong>, you may have seen the following error many times.</p><blockquote><em>“Cannot pull because there are uncommitted changes. Commit, stash, or undo your changes before retrying. See the Output window for details.”</em></blockquote><p>The reason of this error is related to Git’s default settings. When another person pushes a commit to the same branch and your local branch also has changes and is behind, you get this error when you try to pull. Even if the remote changes are not in the same files you are working on, this warning can still appear and it can be annoying.</p><p>Normally in this situation, you need to use methods like stash or stage.</p><pre>git config --global pull.rebase true<br>git config --global rebase.autoStash true</pre><p>If you run the commands above, Git will automatically use stash before each pull. So you will not see this error during pull operations as long as there is no conflict. Your pull process will work more smoothly.</p><p>If a conflict happens, you can choose the correct options in the conflict editor and continue with “accept merge”.</p><p>When I tested conflicts, it showed my local changes like they were remote changes, but this is not a big problem. After resolving the conflict and clicking accept, everything works fine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/0*ekJDyfbkZrbzRcSi.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7653904732e1" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/during-git-pull-uncommitted-changes-problem-and-solution-7653904732e1">During Git Pull: Uncommitted Changes Problem and Solution</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Git Pull Sırasında Uncommitted Changes Sorunu ve Çözümü]]></title>
            <link>https://medium.com/@cngzilhn/git-pull-s%C4%B1ras%C4%B1nda-uncommitted-changes-sorunu-ve-%C3%A7%C3%B6z%C3%BCm%C3%BC-3f26e10ef1c0?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f26e10ef1c0</guid>
            <category><![CDATA[git]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[backend-development]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Wed, 22 Apr 2026 11:25:01 GMT</pubDate>
            <atom:updated>2026-04-22T11:38:52.545Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/354/0*rxglraG1lq9zvTzt.jpg" /></figure><p>“git pull” yaptığınızda aşağıdaki hatayı çok kez görmüşsünüzdür.</p><p>“Cannot pull because there are uncommitted changes. Commit, stash, or undo your changes before retrying. See the Output window for details.”</p><p>Hatanın sebebi git’in default ayarları ile ilgilidir. Aynı branch’e 2. kişi commit atınca ve sizin local branchinizde değişiklik varsa ve geride kalırca pull yaptığınızda yukarıdaki hata ile karşılaşırsınız. Remote branch’deki değişikler sizin çalıştığınız dosyada değilse bile bu uyarı çıkıp sinir bozabiliyor. Bu durumda stash, stage gibi yöntemlere başvurmanız gerekir normal şartlarda.</p><pre>git config --global pull.rebase true<br>git config --global rebase.autoStash true</pre><p>Yukarıdaki komutları sırayla uygularsanız, her pull öncesi git sizin için otomatik olarak stash sistemini çalıştırır. Böylece conflic conflic oluşmadığı sürece hatayı görmeden pull işlemini başarıyla gerçekleştirebilirsiniz.</p><p>Eğer conflic oluşursa conflicdeki doğru seçenekleri seçip accept merge ile devam edebilirsiniz.</p><p>Conflici test ettiğimde localdeki değişikliği “remote branch” değişikliğiymiş gibi gösterdi ama çok büyük bir sorun değil, conflici çözüp accept edince sorun kalmıyor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*UT7SP6B0Y5G1jH2Co5i5eA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f26e10ef1c0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Component-Based MVC]]></title>
            <link>https://medium.com/@cngzilhn/component-based-mvc-718da421ffba?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/718da421ffba</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 21:26:53 GMT</pubDate>
            <atom:updated>2026-03-10T20:23:45.523Z</atom:updated>
            <content:encoded><![CDATA[<h3>Server-Side MVC uygulamaları için modern component mimarisi</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*blb_bMV8kLoNuQHahyB5og.png" /><figcaption><a href="https://www.pexels.com/photo/data-codes-through-eyeglasses-577585/">https://www.pexels.com/photo/data-codes-through-eyeglasses-577585/</a></figcaption></figure><p>Modern frontend dünyasında büyük <strong>bundle dosyaları</strong> giderek yerini <strong>component tabanlı mimarilere</strong> bırakıyor.</p><p>React, Vue ve benzeri modern frontend framework’leri sayesinde artık şu yaklaşım yaygın:</p><ul><li>UI component’lerden oluşur</li><li>her component kendi koduna sahiptir</li><li>yalnızca gereken kod yüklenir</li></ul><p>Ancak birçok <strong>server-side MVC</strong> uygulaması hâlâ eski yaklaşımı kullanıyor:</p><pre>site.css<br>bundle.js</pre><p>Zamanla bu dosyalar büyür ve şu problemler ortaya çıkar:</p><ul><li>kullanılmayan CSS</li><li>gereksiz JavaScript</li><li>zor debug edilen global kod</li><li>riskli refactor</li></ul><p>Bu yazıda, MVC uygulamalarında bu problemi çözmek için basit bir yaklaşım anlatıyorum:</p><blockquote><strong><em>Component-Based MVC</em></strong></blockquote><h3>Fikir</h3><blockquote><em>Component-Based MVC’de bir sayfa, layout ve UI component’lerinin birleşiminden oluşur.</em></blockquote><pre>Page = Layout + Components</pre><p>Her component kendi HTML, CSS ve JS’ini içerir.</p><p>Ve önemli kural:</p><blockquote><em>Component render edilmezse asset yüklenmez. Böylece gereksiz CSS ve JavaScript yüklenmez. HTML’i olmayan bir şeyin CSS ve JS’ine de ihtiyaç yoktur.</em></blockquote><h3>Basit Bir Component Örneği</h3><pre>@{<br>    Html.RegisterStyle(&quot;/styles/components/gallery/gallery.css&quot;);<br>    Html.RegisterScript(&quot;/scripts/gallery.js&quot;, ScriptLocation.Footer);<br>}<br>&lt;div class=&quot;gallery&quot;&gt;<br>    &lt;h2&gt;Gallery&lt;/h2&gt;<br>    &lt;div class=&quot;gallery-images&quot;&gt;<br>        &lt;img src=&quot;/images/gallery1.jpg&quot;&gt;<br>        &lt;img src=&quot;/images/gallery2.jpg&quot;&gt;<br>        &lt;img src=&quot;/images/gallery3.jpg&quot;&gt;<br>    &lt;/div&gt;<br>&lt;/div&gt;</pre><p>Component kendi asset’lerini <strong>register eder</strong>.</p><h3>Page Kullanımı</h3><pre>@{<br>    Html.RegisterStyle(&quot;/styles/pages/home.css&quot;);<br>}<br>&lt;h1&gt;Homepage&lt;/h1&gt;<br>@Html.Partial(&quot;~/Components/Gallery/Gallery.cshtml&quot;)<br>@Html.Partial(&quot;~/Components/Gallery/Gallery.cshtml&quot;)</pre><p>Gallery component iki kez çağrılmış olsa bile:</p><pre>gallery.css → 1 kez yüklenir.<br>gallery.js → 1 kez yüklenir.</pre><h3>SCSS Yapısı</h3><p>Stiller basit bir klasör yapısıyla organize edilebilir:</p><pre>/styles<br>  /components<br>    /gallery<br>      gallery.scss<br>  /pages<br>    home.scss<br>    article.scss<br></pre><ul><li><strong>components/</strong> → tekrar kullanılabilir UI parçaları</li><li><strong>pages/</strong> → sayfaya özel stiller</li></ul><h3>Layout</h3><p>Asset’ler layout içinde render edilir.</p><pre>&lt;head&gt;<br>    @Html.RenderRegisteredStyles()<br>&lt;/head&gt;<br>&lt;body&gt;<br>@RenderBody()<br>    @Html.RenderRegisteredScripts(ScriptLocation.Footer)<br>&lt;/body&gt;</pre><h3>Render Sonucu</h3><p>Sayfa çıktısı şöyle olur:</p><pre>&lt;html&gt;<br>&lt;head&gt;<br>&lt;link rel=&quot;stylesheet&quot; href=&quot;/styles/pages/home.css&quot;&gt;<br>&lt;link rel=&quot;stylesheet&quot; href=&quot;/styles/components/gallery/gallery.css&quot;&gt;<br>&lt;/head&gt;<br>&lt;body&gt;<br>&lt;div class=&quot;gallery&quot;&gt;&lt;/div&gt;<br>&lt;div class=&quot;gallery&quot;&gt;&lt;/div&gt;<br>&lt;script src=&quot;/scripts/gallery.js&quot;&gt;&lt;/script&gt;<br>&lt;/body&gt;<br>&lt;/html&gt;</pre><blockquote><em>Component iki kez render edilse bile asset’ler yalnızca bir kez yüklenir.</em></blockquote><h3>Neden Önemli?</h3><p>Modern frontend mimarileri (React dahil) artık:</p><ul><li>component architecture</li><li>code splitting</li><li>on-demand assets</li></ul><p>üzerine kurulu.</p><p>Component-Based MVC aynı prensibi <strong>server-side rendering dünyasına</strong> getirir.</p><p>MVC değişmez.<br>Sadece View katmanı modernleşir.</p><h3>Özet</h3><p>Component-Based MVC şu prensiplere dayanır:</p><ul><li>UI component’lerden oluşur</li><li>component kendi asset’inin sahibidir</li><li>asset’ler yalnızca gerektiğinde yüklenir</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=718da421ffba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Image Fixer — Instantly Repair Broken Images]]></title>
            <link>https://javascript.plainenglish.io/image-fixer-instantly-repair-broken-images-e2ba81925812?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2ba81925812</guid>
            <category><![CDATA[chrome-extension]]></category>
            <category><![CDATA[qa]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Fri, 06 Mar 2026 19:51:37 GMT</pubDate>
            <atom:updated>2026-03-06T19:51:37.994Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*MX_ZQE1xRgh3K_jM" /></figure><p>Broken or missing images can make <strong>UI testing and frontend development</strong> difficult. I built <strong>Image Fixer</strong>, a Chrome extension that automatically replaces broken images with dynamic placeholders.</p><p>This helps developers, testers, and product teams <strong>continue testing layouts and interfaces without waiting for assets</strong>.</p><p>Instead of dealing with broken &lt;img&gt; tags or missing files, Image Fixer keeps your pages visually stable during development and testing.</p><p>Perfect for:</p><ul><li>Frontend developers</li><li>QA testers</li><li>Product managers</li><li>Anyone testing web interfaces</li></ul><p>If you often deal with <strong>broken images, missing assets, or UI testing issues</strong>, this extension keeps your workflow smooth.</p><p>After installing the extension, simply restart Chrome to activate it.</p><p><a href="https://chromewebstore.google.com/detail/plgcacjbflgmfgklldoliolleahhlgag?utm_source=item-share-cb">Image Fixer - Instantly Repair Broken Images - Chrome Web Store</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2ba81925812" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/image-fixer-instantly-repair-broken-images-e2ba81925812">Image Fixer — Instantly Repair Broken Images</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mobilde Overflow Sorunu: Taşma Yapan Element Nasıl Bulunur?]]></title>
            <link>https://medium.com/@cngzilhn/mobilde-sayfa-neden-sa%C4%9Fa-sola-kayar-h%C4%B1zl%C4%B1-bir-%C5%9Fekilde-nas%C4%B1l-bulunur-04684a353be5?source=rss-307d7cd2a953------2</link>
            <guid isPermaLink="false">https://medium.com/p/04684a353be5</guid>
            <category><![CDATA[sass]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[cengiz ilhan]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 16:34:05 GMT</pubDate>
            <atom:updated>2026-03-06T05:51:41.983Z</atom:updated>
            <content:encoded><![CDATA[<p>Bazen siteyi telefonda açarsın ve sayfa sağa sola kaymaya başlar. Çoğu zaman bunun sebebi <strong>viewport’tan daha geniş bir element olmasıdır</strong>. Yani bir yerde width fazla geliyordur ve bu da body’nin overflow yapmasına sebep olur.</p><p>Sorun şu ki, büyük projelerde hangi elementin bunu yaptığını bulmak bazen zor olabiliyor. DOM’da yüzlerce element oluyor ve tek tek kontrol etmek pek pratik değil.</p><h3>390px’i Referans Alalım</h3><p>Mesela mobil bir layout debug ettiğimizi düşünelim.</p><p>Birçok modern telefonda viewport genişliği yaklaşık <strong>390px</strong> civarında. O yüzden basit bir kontrol yapmak için <strong>390px’i referans olarak kullanabiliriz</strong>.</p><p>Yani body içindeki tüm elementlere bakıp <strong>390px’ten geniş olan var mı</strong> diye kontrol edebiliriz.</p><h3>Küçük Bir Debug Scripti</h3><p>Console’da çalıştırabileceğin basit bir script:</p><pre>const limit = 390;<br>document.body.querySelectorAll(&#39;*&#39;).forEach(el =&gt; {<br>  if (el.offsetWidth &gt; limit) {<br>    el.classList.add(&#39;over-390&#39;);<br>    console.log(&#39;390px geçen element:&#39;, el);<br>  }<br>});</pre><p>İstersen bu elementleri görsel olarak da işaretleyebilirsin:</p><pre>.over-390 {<br>  outline: 2px solid red;<br>}</pre><p>Böylece <strong>390px’i geçen elementler hemen göze çarpar</strong>.</p><h3>Gerçekten Taşma Yapan Elementi Bulmak</h3><p>Bazen elementin width’i normaldir ama pozisyonu yüzünden viewport’u taşırabiliyor.</p><p>Bunu kontrol etmek için şöyle bir yöntem de kullanılabilir:</p><pre>document.body.querySelectorAll(&#39;*&#39;).forEach(el =&gt; {<br>  if (el.getBoundingClientRect().right &gt; window.innerWidth) {<br>    el.classList.add(&#39;overflowing&#39;);<br>    console.log(&#39;Taşma yapan element:&#39;, el);<br>  }<br>});</pre><p>Bu yöntem genelde daha doğru sonuç verir çünkü gerçekten <strong>viewport dışına taşan elementleri</strong> yakalar.</p><h3>Sonuç</h3><p>Mobilde sağa sola kayan sayfalar bazen küçük bir CSS hatasından çıkabiliyor ama bulması uzun sürebiliyor.</p><p>Ama bazen çözüm gerçekten çok basit oluyor. Sadece birkaç satır JavaScript ile hangi elementin layout’u bozduğunu hızlıca görebiliriz.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=04684a353be5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>