<?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[NAVER FE Platform - Medium]]></title>
        <description><![CDATA[NAVER Front End Story - Medium]]></description>
        <link>https://medium.com/naver-fe-platform?source=rss----3a0c875824ff---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>NAVER FE Platform - Medium</title>
            <link>https://medium.com/naver-fe-platform?source=rss----3a0c875824ff---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 23:31:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/naver-fe-platform" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[egjs 2026년 상반기 릴리즈 소식을 전해드립니다]]></title>
            <link>https://medium.com/naver-fe-platform/egjs-2026%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-79a5eb0be40b?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/79a5eb0be40b</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[ai-frontend]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[egj]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Daybrush (Younkue Choi)]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 06:58:45 GMT</pubDate>
            <atom:updated>2026-07-21T08:35:56.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W5gh1igaJEDzDaV0.png" /></figure><h3>egjs, AI Native UI Component 첫걸음</h3><p>egjs는 복잡한 UI 동작을 좀 더 쉽게 구현하도록 돕는 재사용 가능한 UI 컴포넌트를 만드는 데서 시작했습니다.<br>그 목표는 지금도 그대로지만, 개발 환경이 바뀌는 만큼 컴포넌트를 제공하는 방식은 계속 손봐 왔습니다.</p><p>작년 하반기 공지에서, AI로 개발하는 게 당연해지는 흐름에 맞춰 문서·코드·타입 정의·주석·에러 메시지 등 컴포넌트의 모든 정보를 하나의 문서 생태계로 묶고, 문제를 풀다가 정보를 찾느라 막히는 일을 줄이겠다고 말씀드렸습니다.</p><p>이번 릴리즈가 그 첫 결과물입니다.<br>가장 많이 쓰이는 <a href="https://github.com/naver/egjs-flicking">Flicking</a>부터, 사람과 AI가 같이 읽고 활용할 수 있는 문서를 만들었습니다.</p><h3>이번에 한 일</h3><p>지난 공지에서 정리한 세 가지, 데모 확충 / 옵션의 역할·조합·주의사항 정리 / 사람과 AI가 함께 쓸 수 있는 형태를 <a href="https://github.com/naver/egjs-flicking">Flicking</a> 문서에 실제로 반영했습니다.</p><h3>1. <a href="https://naver.github.io/egjs-flicking/llms.txt">llms.txt</a> — AI를 위한 진입점</h3><p>이제 Flicking 문서는 표준 형식의 <a href="https://naver.github.io/egjs-flicking/llms.txt">llms.txt</a>를 제공합니다. AI 에이전트가 사전 지식 없이도 Flicking이 뭔지, 어떤 패키지를 써야 하는지, 무엇을 어디서 찾는지 한 번에 파악하도록 문서 전체 지도를 담았습니다. 사람이 보는 페이지와 별개로, 각 문서를 AI가 그대로 읽을 수 있는 .md 형태(llm-docs/...)로도 제공합니다. &quot;API랑 옵션 설명만 봐서는 실제로 뭘 하는 옵션인지 감이 안 온다&quot;는 문제를 사람과 AI 양쪽에서 같은 방식으로 풀 수 있게 된 셈입니다.</p><h4>llms.txt 쓰는 법</h4><p>1) AI 코딩 도구에 컨텍스트로 넘기기</p><p>Cursor, Claude, Copilot처럼 문서 URL을 컨텍스트로 받는 도구에 위 주소를 그대로 주면, 에이전트가 llms.txt에서 작업에 필요한 문서를 알아서 찾아 읽습니다.</p><pre>이 문서를 참고해서 작업해줘: https://naver.github.io/egjs-flicking/llms.txt<br>요구사항: 무한 루프로 도는 가로 캐러셀을 React로 만들고, 양옆에 이전/다음 버튼을 붙여줘.</pre><p>2) 에러 원인을 볼 때</p><p>에러 코드만으로도 원인을 좁힐 수 있습니다.</p><pre>Flicking에서 이런 에러가 나는데 원인이 뭐야? (err.code 확인)<br>문서: https://naver.github.io/egjs-flicking/llms.txt</pre><p>에이전트가 llms.txt를 보고, 해당 코드가 서비스 코드 문제인지 Flicking 내부 동작 문제인지 구분해서 알려줍니다.</p><p>3) 특정 문서만 바로 읽기<br>llms.txt의 링크는 전부 .md 원문을 가리키니, 필요한 문서만 골라 직접 열어봐도 됩니다.</p><h3>2. 데모 6개에서 47개로</h3><p>기존 6개뿐이던 데모를 4개 카테고리·47개로 늘려, 주요 옵션 대부분을 실제 동작으로 확인할 수 있게 했습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r6_H0MoCkfCPUxCbUCGcOQ.png" /></figure><p><a href="https://naver.github.io/egjs-flicking/docs/demos/basic/circular">https://naver.github.io/egjs-flicking/docs/demos/basic/circular</a></p><p>데모마다 JavaScript / React / Vue@3 코드 탭이 있고, 페이지 안에서 바로 고쳐 실행하는 <strong>라이브 에디터(Open Sandbox)</strong>도 넣었습니다.</p><p>따로 설정할 것 없이 브라우저에서 옵션을 바꿔가며 동작을 바로 볼 수 있습니다.</p><h3>3. 문서끼리 연결하고 UX 정리</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJbhOfzJH0kAkqrqLbRYaA.png" /></figure><p><a href="https://naver.github.io/egjs-flicking/docs/api/classes/Flicking">https://naver.github.io/egjs-flicking/docs/api/classes/Flicking</a></p><p>따로 놀던 데모·옵션·타입·API 문서를 서로 이었습니다. 어디서 시작하든 필요한 정보로 자연스럽게 넘어가도록 하는 게 목적이었고, 크게 네 가지를 연결했습니다.</p><ul><li><strong>타입에 대한 링크 </strong>— 데모와 옵션 설명에서 해당 옵션의 타입 정의로 바로 이동합니다. 단순히 페이지를 여는 게 아니라 API 문서의 정확한 위치를 가리키는 딥 링크입니다.</li></ul><pre>align         → /docs/api/interfaces/FlickingOptions#align<br>panelsPerView → /docs/api/interfaces/FlickingOptions#panelsperview<br>circular      → /docs/api/interfaces/FlickingOptions#circular</pre><ul><li><strong>since</strong> — 각 옵션·메서드에 추가된 버전을 같이 적어, 지금 쓰는 버전에서 되는 API인지 바로 알 수 있습니다. (예: panelsPerView since v4.2.0, useCSSOrder since v4.15.0)</li><li><strong>데모 연결</strong> — 하나의 데모에서 관련 옵션·연관 데모로 이어지고, 가이드 문서 안에도 간이 데모와 프레임워크 코드 탭(JS/React/Vue3)이 들어 있어 설명과 동작을 같은 화면에서 볼 수 있습니다. (예: Alignment → Circular, Panels Per View)</li><li><strong>IDE 툴팁 연결</strong> — 문서에 나오는 타입·since·주의사항은 전부 패키지에 동봉된 타입 정의(.d.ts)와 TSDoc 주석에서 나옵니다. 그래서 같은 설명이 VS Code 같은 IDE에서 코드를 짤 때 타입 시그니처가 하이라이트된 hover 툴팁으로 그대로 뜹니다. 문서 사이트를 따로 안 열어도 에디터 안에서 바로 확인되고, AI 에이전트도 같은 정보를 근거로 씁니다.</li></ul><h3>이제 되는 것들</h3><p>지난 공지에서 목표로 잡았던 시나리오들이 Flicking 문서에서 이렇게 돌아가기 시작했습니다.</p><ul><li><strong>사용 가이드</strong>: AI 에이전트가 llms.txt와 .md 문서를 보고 만들려는 UI에 맞는 옵션을 안내하고, 데모에 정리된 조합·주의사항을 근거로 잘못된 옵션 조합을 미리 걸러냅니다.</li><li><strong>이슈 원인 분석</strong>: FlickingErrors의 에러 코드와 동작 흐름 설명으로, 지금 문제가 서비스 코드 탓인지 Flicking 내부 탓인지 빠르게 구분합니다.</li><li><strong>컨트리뷰션</strong>: 각 페이지의 Edit this page와 상호 링크 구조 덕에, 문서를 보다가 개선·기여로 자연스럽게 넘어갈 수 있습니다.</li><li><strong>자연어로 UI 만들기</strong>: &quot;썸네일 하단 무한 루프 캐러셀&quot; 같은 요구를 llms.txt·데모 조합을 근거로 필요한 Flicking 옵션·플러그인 조합으로 매핑해 실행 가능한 코드까지 만들어냅니다.</li></ul><h3>앞으로</h3><p>이번 <a href="https://github.com/naver/egjs-flicking">Flicking</a> 문서 개편은 “egjs, AI Native UI Component” 방향을 처음 적용해 본 사례입니다.</p><p>llms.txt·.md 문서, 옵션 단위 데모, Summary·Notes·상호 링크로 짜인 페이지 구성을 하나의 패턴으로 두고, 다른 egjs 컴포넌트에도 차차 적용해 갈 계획입니다.</p><p>egjs는 기능을 많이 넣은 라이브러리라기보다, 문제를 푸는 과정 전체를 거드는 UI 컴포넌트 생태계이고 싶습니다.<br>구조가 분명하고 동작이 예측 가능하며 AI와 같이 굴러가는 개발 경험을 목표로 계속 다듬어 가겠습니다.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79a5eb0be40b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/egjs-2026%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-79a5eb0be40b">egjs 2026년 상반기 릴리즈 소식을 전해드립니다</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Release note of egjs(First Half 2026)]]></title>
            <link>https://medium.com/naver-fe-platform/release-note-of-egjs-first-half-2026-a97e8edc7055?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/a97e8edc7055</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[egj]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[ai-frontend]]></category>
            <dc:creator><![CDATA[Daybrush (Younkue Choi)]]></dc:creator>
            <pubDate>Tue, 21 Jul 2026 06:57:54 GMT</pubDate>
            <atom:updated>2026-07-21T08:36:37.469Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*W5gh1igaJEDzDaV0.png" /></figure><h3>egjs, the First Step Toward AI Native UI Components</h3><p>egjs began as an effort to build reusable UI components that make complex UI behaviors easier to implement. That goal hasn’t changed, but as development environments evolve, we’ve kept reworking <em>how</em> we deliver those components.</p><p>In last year’s second-half announcement, we said that — in step with a world where developing with AI is becoming the norm — we would bundle all of a component’s information (docs, code, type definitions, comments, error messages) into a single documentation ecosystem, so you get stuck hunting for information far less often while solving a problem.</p><p>This release is the first result of that effort.</p><p>Starting with <a href="https://github.com/naver/egjs-flicking">Flicking</a>, our most widely used component, we’ve built documentation that both people and AI can read and use together.</p><h3>What We Did</h3><p>We took the three things laid out in our previous announcement — expanding the demos, organizing the roles/combinations/caveats of options, and making the docs usable by both people and AI — and actually applied them to the Flicking documentation.</p><h3>1. llms.txt — An Entry Point for AI</h3><p>Flicking’s documentation now provides a standard-format <a href="https://naver.github.io/egjs-flicking/llms.txt">llms.txt</a>. It contains a full map of the documentation so that an AI agent, with no prior knowledge, can grasp in one pass what Flicking is, which package to use, and where to find what. Separate from the human-facing pages, each document is also provided in .md form (llm-docs/...) that AI can read as-is. This means the problem of &quot;just reading the API and option descriptions doesn&#39;t tell me what an option actually does&quot; can now be solved the same way for both people and AI.</p><p><strong>How to use llms.txt</strong></p><p>1) Pass it as context to an AI coding tool</p><p>For tools that take a documentation URL as context — like Cursor, Claude, or Copilot — just hand them the address above, and the agent will find and read the docs it needs for the task from llms.txt.</p><pre>Please work using this document as reference: https://naver.github.io/egjs-flicking/llms.txt<br>Requirement: Build an infinitely looping horizontal carousel in React, with previous/next buttons on either side.</pre><p>2) Diagnosing the cause of an error</p><p>You can narrow down the cause from the error code alone.</p><pre>I&#39;m getting this error in Flicking—what&#39;s the cause? (check err.code)<br>Docs: https://naver.github.io/egjs-flicking/llms.txt</pre><p>The agent reads llms.txt and tells you whether that code points to a problem in your service code or in Flicking&#39;s internal behavior.</p><p>3) Reading just a specific document directly</p><p>Since every link in llms.txt points to the raw .md source, you can also pick out and open only the document you need.</p><h3>2. From 6 Demos to 47</h3><p>We expanded the demos from just 6 to 47 across 4 categories, so you can verify most of the major options through real, running behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*r_vv1QZJiBI0Pjuo-pWLNQ.png" /></figure><p><a href="https://naver.github.io/egjs-flicking/docs/demos/basic/circular">https://naver.github.io/egjs-flicking/docs/demos/basic/circular</a></p><p>Each demo has JavaScript / React / Vue@3 code tabs, and we’ve added a <strong>live editor (Open Sandbox)</strong> that lets you edit and run right on the page.</p><p>With no separate setup, you can change options in the browser and see the behavior immediately.</p><h3>3. Connecting Docs Together and Cleaning Up the UX</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJbhOfzJH0kAkqrqLbRYaA.png" /></figure><p><a href="https://naver.github.io/egjs-flicking/docs/api/classes/Flicking">https://naver.github.io/egjs-flicking/docs/api/classes/Flicking</a></p><p>We linked together the demos, options, types, and API docs that used to stand apart. The goal was to make it flow naturally toward the information you need no matter where you start, and we connected four things in particular:</p><ul><li><strong>Links to types</strong> — From the demos and option descriptions, you jump straight to that option’s type definition. These aren’t just links that open a page; they’re deep links pointing to the exact spot in the API docs.</li></ul><pre>align → /docs/api/interfaces/FlickingOptions#align<br>panelsPerView → /docs/api/interfaces/FlickingOptions#panelsperview<br>circular → /docs/api/interfaces/FlickingOptions#circular</pre><ul><li><strong>since</strong> — Each option and method now notes the version it was added in, so you can tell right away whether an API works in the version you’re using. (e.g. panelsPerView since v4.2.0, useCSSOrder since v4.15.0)</li><li><strong>Demo connections</strong> — One demo leads to related options and related demos, and the guide docs themselves embed mini-demos and framework code tabs (JS/React/Vue3), so you can see the explanation and the behavior on the same screen. (e.g. Alignment → Circular, Panels Per View)</li><li><strong>IDE tooltip integration</strong> — The types, since notes, and caveats shown in the docs all come from the type definitions (.d.ts) and TSDoc comments bundled with the package. So the same explanations appear as hover tooltips with highlighted type signatures while you write code in an IDE like VS Code. You can check them right inside the editor without opening the docs site separately, and AI agents draw on the same information.</li></ul><h3>What Works Now</h3><p>The scenarios we set as goals in the previous announcement have started to work like this in the Flicking documentation:</p><ul><li><strong>Usage guidance:</strong> An AI agent reads llms.txt and the .md docs, recommends the right options for the UI you want to build, and—based on the combinations and caveats organized in the demos—filters out invalid option combinations in advance.</li><li><strong>Issue root-cause analysis:</strong> Using the FlickingErrors error codes and the behavior-flow explanations, it quickly distinguishes whether the current problem is due to your service code or Flicking’s internals.</li><li><strong>Contribution:</strong> Thanks to the “Edit this page” on each page and the cross-linking structure, you can move naturally from reading the docs into improving and contributing.</li><li><strong>Building UI in natural language:</strong> A request like “an infinite-loop carousel below the thumbnails” gets mapped — based on llms.txt and demo combinations—to the necessary combination of Flicking options and plugins, all the way to runnable code.</li></ul><h3>What’s Next</h3><p>This <a href="https://github.com/naver/egjs-flicking">Flicking</a> documentation overhaul is our first attempt at applying the “<strong>egjs, AI Native UI Component</strong>” direction.</p><p>We’ll treat this composition — llms.txt and .md docs, per-option demos, and pages built from Summary, Notes, and cross-links—as a single pattern, and gradually apply it to the other egjs components as well.</p><p>egjs wants to be less a library crammed with features and more a UI component ecosystem that supports the entire problem-solving process. We’ll keep refining it toward a development experience that is clearly structured, predictable in behavior, and runs alongside AI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a97e8edc7055" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/release-note-of-egjs-first-half-2026-a97e8edc7055">Release note of egjs(First Half 2026)</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[egjs 2025년 하반기 릴리즈 소식을 전해드립니다]]></title>
            <link>https://medium.com/naver-fe-platform/egjs-2025%EB%85%84-%ED%95%98%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-9d354455dc54?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/9d354455dc54</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[egj]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Daybrush (Younkue Choi)]]></dc:creator>
            <pubDate>Mon, 29 Dec 2025 09:00:24 GMT</pubDate>
            <atom:updated>2025-12-29T09:00:23.568Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nq9dH5fKf-UtU8W1vMEqrw.png" /><figcaption>egjs 3th concept logo</figcaption></figure><h3>egjs, AI Native UI Component</h3><p>egjs는 복잡한 UI 동작을 보다 쉽게 구현할 수 있도록 재사용 가능한 UI 컴포넌트를 제공하는 것을 목표로 시작되었습니다.</p><p>이 방향성은 지금까지도 egjs의 중심에 있으며, egjs는 변화하는 개발 환경에 맞춰 지속적으로 구조와 제공 방식을 조정해 왔습니다.</p><p>브라우저와 입력 환경의 다양화, 프레임워크 생태계의 확장에 대응해 온 egjs는 이제 AI 기반 개발 환경이 보편화되는 전환점을 맞이하고 있습니다.</p><p>AI를 활용한 개발 방식에서는 코드 작성뿐 아니라 문서를 탐색하고 맥락을 이해하며 문제를 해결하는 전체 흐름이 중요해지고 있습니다. 이에 따라 egjs 팀은 사용자 인터뷰와 내부 분석을 통해 현재 egjs 사용 과정의 구조적인 문제를 재정리했습니다.</p><h4>문제 인식</h4><p>egjs 사용자는 문제 해결 과정에서 문서, 사례, 코드를 탐색하게 되지만</p><ul><li>API와 옵션의 설명만으로는 실제 역할과 맥락을 이해하기 어렵고</li><li>사례와 코드는 조건과 구조가 복잡해 탐색 비용이 높으며</li><li>이러한 어려움은 사람뿐 아니라 egjs를 이해해야 하는<strong> AI에게도 동일하게 적용</strong>됩니다.</li></ul><p>그 결과, 정보 탐색 자체가 문제 해결의 장애물로 작용하고 있음을 확인했습니다.</p><h4>목표하는 개발 시나리오</h4><p>egjs는 AI 에이전트를 활용한 개발 환경에서 다음과 같은 경험이 자연스럽게 이루어지기를 목표로 합니다.</p><ul><li>개인화된 사용 가이드 지원: 구현하려는 UI 스펙에 맞는 옵션을 빠르게 안내하고, 잘못된 옵션 조합을 사전에 방지</li><li>이슈 원인 분석 지원: 발생한 문제가 서비스 코드인지 egjs 내부 동작인지 신속히 구분</li><li>컨트리뷰션 흐름 지원: 사용자가 문제 해결을 넘어 자연스럽게 기여로 이어질 수 있는 환경 제공</li></ul><h4>egjs의 선택과 실행 방향</h4><p>egjs는 사용자 문서, 코드, 타입 정의, 주석, 에러 메시지 등 컴포넌트의 모든 정보를 하나의 문서 생태계로 정의하고 문제 해결 과정에서 정보 탐색이 방해 요소가 되지 않도록 개선을 진행합니다.</p><ul><li>사용자 문서 개선<br>실제 사용 시나리오 중심의 데모 확충<br>옵션의 역할, 조합 관계, 주의 사항 정리<br>컴포넌트 동작 흐름과 내부 가정 설명 강화</li><li>코드 기반 정보 개선<br>TypeScript 타입과 주석을 활용한 의미 표현 강화<br>에러 메시지 및 처리 규칙 정비<br>내부 구조 개선을 통한 예측 가능성 향상</li></ul><p>이번 개선은 단순한 문서 정비를 넘어 사람과 AI가 함께 egjs를 이해하고 활용할 수 있는 기반을 만드는 것을 목표로 합니다.</p><h3>📣 알립니다</h3><h4>네이버 모바일 검색 OOTD(Outfit Of The Day) 키워드에 @egjs/grid가 적용되었습니다.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/806/1*VMxnWvjO79NjPwC0czUNrA.png" /><figcaption>OOTD 검색 결과</figcaption></figure><p><a href="https://m.search.naver.com/search.naver?sm=mtb_hty.top&amp;query=%EC%98%A4%EB%8A%98%EC%9D%98+%EC%98%B7%EC%B0%A8%EB%A6%BC"><strong>OOTD 검색 결과</strong></a>는 stretchItemSize 옵션을 사용하여 아이템의 최소, 최대 크기(높이)를 제한하는 형태의 UI를 만들었습니다.</p><pre>import { MasonryGrid } from &quot;@egjs/react-grid&quot;;<br><br>&lt;MasonryGrid<br>   align=&quot;stretch&quot;<br>   column={2}<br>   gap={10}<br>   useResizeObserver={true}<br>   columnSizeRatio={true}<br>   // 아이템의 높이는 width:height 비율로 1:1로 최소 높이로 제한하고 3:4 비율로 최대 높이를 제한합니다.<br>   stretchItemSize={[&quot;1:1&quot;, &quot;3:4&quot;]}&gt;<br>   &lt;Item /&gt;<br>   &lt;Item /&gt;<br>   &lt;Item /&gt;<br>&lt;/MasonryGrid&gt;</pre><h4>React 19의 findDOMNode 제거로 인한 React Flicking 사용 방법 가이드 변경</h4><p>기존 Flicking은 ref 또는 findDOMNode을 사용하여 element 파악을 하였지만 react 19 부터 findDOMNode이 삭제가 됐으며 Flicking 4.14.0부터 useFindDOMNode prop을 사용할 수 없고 ref 방식만을 지원합니다.</p><pre>// App<br>&lt;Flicking&gt;<br>  &lt;Item /&gt;<br>  &lt;Item /&gt;<br>  &lt;Item /&gt;<br>&lt;/Flicking&gt;</pre><pre>// AS-IS<br>function Item() {<br>  return &lt;div&gt;&lt;/div&gt;;<br>}</pre><pre>// TO-BE (&lt; 19)<br>const Item = React.forwardedRef((props, ref) =&gt; {<br> return &lt;div ref={ref}&gt;&lt;/div&gt;<br>});</pre><pre>// TO-BE (19)<br>function Item(props) {<br> return &lt;div ref={props.ref}&gt;&lt;/div&gt;<br>});</pre><h4>egjs 공식 지원 대상 프레임워크 및 최소 요구 사항 변경 사전 안내</h4><p><strong>주요 변경 사항</strong></p><ul><li>공식 지원 프레임워크 유지: React, Vue 3</li><li>공식 지원 종료(단계적): Angular, Vue 2, Svelte, Preact</li></ul><p>현재 프론트엔드 생태계는 소수의 핵심 프레임워크를 중심으로 점차 수렴하고 있으며 AI 기반 개발 환경에서도 표준화된 구조와 높은 사용률을 가진 프레임워크가<br>문제 해결 효율과 도구 활용 측면에서 중요한 역할을 하고 있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dhZFo516txl2105CdbeXng.png" /><figcaption>Flicking Framework Usage Chart</figcaption></figure><p>egjs 팀은 이러한 흐름에 맞춰 egjs 프레임워크용 컴포넌트들의 사용 현황 데이터를 분석했고 그 결과 React와 Vue 3 기반 패키지의 사용 비중이 다른 프레임워크 대비<br>압도적으로 높은 수준임을 확인했습니다.</p><p>이에 따라 egjs는 앞으로 React와 Vue 3를 공식 지원 프레임워크로 유지하며,<br>나머지 프레임워크(Angular, Vue 2, Svelte, Preact)에 대해서는 공식 지원을 단계적으로 종료할 예정입니다.</p><p>공식 지원 종료는 신규 기능 개발, 테스트, 문서화 대상에서 제외됨을 의미하며 기존 패키지와 이미 배포된 릴리즈 버전은 그대로 사용 가능합니다.</p><p>또한 기존 사용자들에게 이슈가 될 수 있는 사항들은 내부적으로 조사한 후에 개발 환경의 최소 버전(react, typescript)을 업데이트를 고려하고 있습니다.</p><h3>🔖 egjs 릴리즈 내역</h3><h4><a href="https://naver.github.io/egjs-flicking/">@egjs/flicking</a> 4.15.0 (2025–11–25)</h4><ul><li>무한 드래깅을 방지하는 animationThreshold 옵션이 추가되었습니다.</li><li>DOM reload(iframe)을 방지하는 css order을 사용하는 useCSSOrder 옵션이 추가되었습니다.</li><li>useFindDOMNode가 옵션이 제거되었습니다.</li></ul><h4><a href="https://naver.github.io/egjs-infinitegrid/">@egjs/infinitegrid</a> 4.13.0 (2025–12–29)</h4><ul><li>화면 사이즈에 따라 비율대로 최소, 최대 크기까지 늘릴 수 있는 옵션 strecthItemSize, stretchContainerSize를 추가했습니다.</li><li>resizeScroll(scroll 위치 갱신)에 따른 리렌더링 조건을 수정했습니다.</li><li>화면 사이즈에 따라 비율대로 최소, 최대 크기까지 늘릴 수 있는 옵션 stretchOutline, strecthItemSize, stretchContainerSize를 추가했습니다.</li><li>성능 개선을 위한 보이지 않는 아이템들의 element를 제거하는 useDetachedRecycle 옵션이 추가되었습니다.</li><li>데이터의 끝을 알리는 isReachStart, isReachEnd 옵션, 이벤트 속성이 추가되었습니다.</li></ul><h4><a href="https://github.com/naver/egjs-grid/releases/tag/1.18.0">@egjs/grid</a> 1.18.0 (2025–12–12)</h4><ul><li>화면 사이즈에 따라 비율대로 최소, 최대 크기까지 늘릴 수 있는 옵션 strecthItemSize, stretchContainerSize를 추가했습니다.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d354455dc54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/egjs-2025%EB%85%84-%ED%95%98%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-9d354455dc54">egjs 2025년 하반기 릴리즈 소식을 전해드립니다</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[egjs 2025년 상반기 릴리즈 소식을 전해드립니다]]></title>
            <link>https://medium.com/naver-fe-platform/egjs-2025%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-ddabd7262d14?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/ddabd7262d14</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[egj]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[open-source]]></category>
            <dc:creator><![CDATA[Malangfox]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 08:55:48 GMT</pubDate>
            <atom:updated>2025-07-03T08:55:47.907Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*KHP6jgO3ZfagJET2hqxw-w.png" /></figure><p>네이버의 FE 오픈소스 컴포넌트 그룹인 <a href="https://naver.github.io/egjs/">egjs</a>의 25년 상반기 릴리즈 소식을 전해드립니다.</p><p>이번 정기 릴리즈에서는 <a href="https://github.com/naver/egjs-flicking">@egjs/flicking</a> 컴포넌트에 새로 추가된 기능들과 Flicking 사용 시 놓치기 쉬운 부분들에 대한 노하우를 소개합니다.</p><p>— -</p><h3><strong>🚀 새로운 기능들</strong></h3><h4><strong>Flicking의 상태 변화를 감지하는 Reactive API가 추가되었습니다.</strong></h4><p>기존의 Flicking은 외부 디자인 시스템 컴포넌트나 커스터마이징된 UI를 사용할 때 Flicking의 여러 이벤트를 구독해서 이벤트 기반으로 상태를 업데이트해야 하는 불편함이 있었습니다.</p><p>다음 버전의 Flicking부터 상태 변화를 반응형으로 관리할 수 있는 Reactive API가 추가되었습니다.</p><p>Reactive API에서 제공하는 상태들을 통해 기존의 이벤트 기반 대신 상태 기반으로 UI를 갱신할 수 있습니다.</p><p>다음 버전의 Flicking에서는 아래의 상태들을 새롭게 제공할 예정입니다.</p><ul><li>첫 번째 패널에 도달했는지 여부를 나타내는 `isReachStart`</li><li>마지막 패널에 도달했는지 여부를 나타내는 `isReachEnd`</li><li>전체 패널의 갯수 `totalPanelCount`</li><li>현재 활성화된 패널의 인덱스 `currentPanelIndex`</li><li>전체 Flicking 영역의 스크롤 진행율 `progress`</li><li>패널 간 스크롤 진행율 `indexProgress`</li></ul><p>이렇게 제공되는 상태들을 통해 MUI 및 Ant Design과 같은 외부 UI 컴포넌트와 보다 쉽게 조합해서 사용할 수도 있습니다.</p><p>예를 들어, Flicking의 플러그인 Pagination을 사용하는 대신 Headless UI 컴포넌트처럼 상태에 원하는 스타일을 입혀 사용하거나 외부 디자인 시스템 컴포넌트와 조합할 수 있습니다.</p><p>다음 데모는 Reactive API의 상태를 통해 MUI의 페이지네이션을 Flicking에 도입한 예시입니다. (<a href="https://naver.github.io/egjs-flicking/Demos#pagination">데모 링크</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mpQBGhCl3moG3y9JV6NnfA.gif" /></figure><pre>import React from &quot;react&quot;;<br>import Flicking, { useFlickingReactiveAPI } from &quot;@egjs/react-flicking&quot;;<br>import Pagination from &quot;@mui/material/Pagination&quot;;<br>export default function PaginationExample() {<br>  const flickingRef = React.useRef(null);<br>  const {<br>    currentPanelIndex,<br>    totalPanelCount,<br>    moveTo<br>  } = useFlickingReactiveAPI(flickingRef);<br>  const handlePageChange = (event, page) =&gt; {<br>    moveTo(page - 1); // MUI Pagination은 1부터 시작<br>  };<br>  return (<br>    &lt;div&gt;<br>      &lt;Flicking ref={flickingRef}&gt;<br>        {panels.map((panel, index) =&gt; (<br>          &lt;div key={index} className=&quot;panel&quot;&gt;{panel}&lt;/div&gt;<br>        ))}<br>      &lt;/Flicking&gt;<br>      &lt;Pagination<br>        page={currentPanelIndex + 1}<br>        count={totalPanelCount}<br>        onChange={handlePageChange}<br>      /&gt;<br>    &lt;/div&gt;<br>  );<br>}</pre><p>그 외에도 Reactive API에서 제공하는 상태들을 통해 다양한 구현을 할 수 있습니다.</p><p><strong>Flicking을 조작하는 버튼의 활성화 여부와 `isReachStart`, `isReachEnd`를 연동하는 구현</strong> (<a href="https://naver.github.io/egjs-flicking/Demos#prev--next-button">데모 링크</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SFSuUjV0vDnOn6VAxRbUZg.gif" /></figure><p><strong>Flicking의 진행도를 나타내는 `progress` 를 사용한 Progress Bar 구현</strong> (<a href="https://naver.github.io/egjs-flicking/Demos#progress-bar">데모 링크</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Pnj3rw2ajl4xGHXSQPXR6Q.gif" /></figure><p><strong>패널 간 스크롤 진행율을 나타내는 `indexProgress` 를 사용한 패널 넘김 효과 구현</strong> (<a href="https://naver.github.io/egjs-flicking/Demos#parallax">데모 링크</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4bPiE_UsHIiM4bX5EvZ9aw.gif" /></figure><h4><strong>Flicking 내부 요소의 크기 변화를 추적하는 `observePanelResize` 옵션이 추가되었습니다.</strong></h4><p>Flicking에는 각 패널의 높이에 맞게 전체 영역의 높이를 조정하는 `adaptive` 옵션이 존재합니다.</p><p>이 옵션이 활성화되어있을 때 Flicking에서 현재 표시 중인 패널이 변경될 때 새로운 패널에 맞게 Flicking의 높이가 고정됩니다.</p><p>그러나 서비스를 개발하는 과정에서 현재 표시 중인 패널의 로딩이 완료되었을 때 패널의 높이가 변경될 수 있는 경우가 존재했습니다.</p><p>서버 사이드 렌더링으로 Flicking과 내부 패널들을 모두 표시한 이후 클라이언트 사이드 렌더링으로 패널 내부 데이터를 fetch해왔을 때, 기존의 Flicking은 `adaptive` 옵션으로 높이가 고정된 상태에서 이와 같이 패널의 높이가 변하더라도 Flicking의 높이를 갱신하지 못했습니다.</p><p>이러한 경우를 대응하기 위해 Flicking 내부 엘리먼트의 크기 변화를 추적하는 `observePanelResize` 옵션이 추가되었습니다.</p><p>`observePanelResize` 옵션을 활성화하면 `adaptive` 옵션으로 Flicking의 높이가 고정된 상태라도 내부 요소의 크기 변경에 따라 전체 영역의 높이를 재조정하게 됩니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ykmIX_Yn62K-hOCgN0soUQ.gif" /></figure><p>위 예시는 `observePanelResize` 옵션이 활성화되지 않았을 때와 활성화되었을 때 Panel의 높이 변경에 따른 동작 차이를 나타냅니다.</p><p>위와 같은 사례 외에도 Flicking을 조작하는 도중 패널의 가로 크기가 변경될 수 있는 경우에 대해서도 Flicking의 움직임이 어긋나는 현상을 방지할 수 있습니다.</p><p>`adaptive` 옵션에 더해 패널 내부의 로딩 등 실시간으로 패널의 크기가 변하는 경우 `observePanelResize` 옵션을 사용해보세요.</p><p>— -</p><h3><strong>🛠️ 눈에 띄는 이슈들</strong></h3><h4><strong>Flicking에 커스텀 스타일을 적용할 때 확인해주세요!</strong></h4><p>서비스를 개발하며 Flicking의 기본 스타일을 사용하는 대신 클래스에 적용된 스타일을 임의로 설정하는 경우가 있습니다.</p><p>하나의 페이지 안에 Flicking을 사용하는 서로 다른 두 서비스가 표시된다면 서로 다른 스타일을 가진 두 Flicking이 노출되게 됩니다.</p><p>아래의 예시는 1번 Flicking의 `flicking-camera` 클래스에 배경 색상을 지정했을 때 2번 Flicking의 스타일이 영향을 받아 망가지는 예시입니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNgWCEnk3goM4wJ6_dgO9g.png" /></figure><p>이렇게 Flicking에서 사용되는 클래스인 `flicking-viewport` 와 `flicking-camera` 클래스에 직접 스타일을 입히면 다른 서비스의 Flicking 스타일이 영향을 받을 수 있습니다.</p><p>Flicking의 구성 요소에 스타일을 입힐 때는 다음 예시와 같이 특정 서비스의 Flicking 내에만 스타일이 적용되게끔 사용하는 것을 권장드립니다.</p><pre>.service-root {<br>  .flicking-viewport {<br>    …<br>  }<br>}</pre><p>그 외에도 react-flicking을 사용하는 경우 `cameraClass` 옵션을 통해 flicking-camera 엘리먼트에 적용할 클래스명을 임의로 설정해서 해당 클래스에만 스타일을 입히는 방법으로 스타일 충돌을 방지할 수 있습니다.</p><p>— -</p><h3><strong>📰 새로운 소식</strong></h3><h4><strong>JustifiedGrid의 확장 옵션 stretch를 사용하는 서비스가 배포되었습니다.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qglV9qupy3ruLQuf-KRhdQ.png" /></figure><p>2024년 상반기 릴리즈에서 <a href="https://github.com/naver/egjs-infinitegrid">@egjs/infinitegrid</a>의 JustifiedGrid에 추가된 `stretch` 옵션은 JustifiedGrid의 확장 옵션으로 주어진 높이를 유지한 채 아이템의 비율을 왜곡해서 너비를 조정하는 기능을 가졌습니다.</p><p>2025년 상반기에 걸쳐 해당 옵션의 성능 최적화가 이루어진 뒤 `stretch` 옵션을 사용하는 이미지 검색 서비스가 처음으로 배포되었습니다.</p><p>이 과정에서 이미지가 빠르게 로딩되었을 때 @egjs/imready 컴포넌트에서 `preReady` 이벤트가 발생하지 않던 현상 또한 수정되었습니다.</p><p>이제 네이버의 검색 서비스에서 개선된 @egjs/infinitegrid를 만나보세요!</p><p>— -</p><h3>🔖 egjs 릴리즈 내역</h3><h4><a href="https://github.com/naver/egjs-flicking"><strong>@egjs/flicking</strong></a><strong> 4.14.0 (2025–06–30)</strong></h4><ul><li>Flicking의 상태 변화를 감지하는 Reactive API가 추가되었습니다.</li><li>React에서 Panel의 className이 변경될 때 상태가 갱신되지 않던 현상을 수정했습니다.</li><li>adaptive가 true일 때 Panel의 높이 변경을 감지하고 viewport의 크기를 변경하는 observePanelResize 옵션이 추가되었습니다.</li><li>Flicking의 드래그를 마쳤을 때 입력 방향이 잘못 인식되던 현상이 수정되었습니다.</li><li>Panel의 높이가 변경될 때 resize 이벤트가 무한 루프로 발생하던 현상이 수정되었습니다.</li><li>viewport가 resize될 때 Panel들의 재렌더링을 막는 optimizeSizeUpdate 옵션이 추가되었습니다.</li></ul><h4><a href="https://github.com/naver/egjs-conveyer"><strong>@egjs/conveyer</strong></a><strong> 1.8.0 (2025–04–18)</strong></h4><ul><li>사용자의 입력을 활성화 및 비활성화하는 enableInput 메서드와 disableInput 메서드가 추가되었습니다.</li><li>소수점 단위 너비를 가진 엘리먼트를 대상으로 애니메이션 재생 이후 현재 위치가 올바르게 인식되지 않던 현상을 수정했습니다.</li></ul><h4><a href="https://github.com/naver/egjs-axes"><strong>@egjs/axes</strong></a><strong> 3.9.2 (2025–06–05)</strong></h4><ul><li>PanInput에서 드래그를 마쳤을 때 입력 방향이 잘못 인식되던 현상이 수정되었습니다.</li><li>PanInput에서 inputType 옵션 중 사용 가능한 입력 수단이 없는 경우 PanInput이 활성화되지 않도록 변경되었습니다.</li></ul><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*uc-ZJmHAIeWdTz6RPHsJ8Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddabd7262d14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/egjs-2025%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-ddabd7262d14">egjs 2025년 상반기 릴리즈 소식을 전해드립니다</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Release note of egjs(First Half 2025)]]></title>
            <link>https://medium.com/naver-fe-platform/release-note-of-egjs-first-half-2025-e860deaef099?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/e860deaef099</guid>
            <category><![CDATA[egj]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Malangfox]]></dc:creator>
            <pubDate>Thu, 03 Jul 2025 08:55:11 GMT</pubDate>
            <atom:updated>2025-07-03T08:55:11.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*KHP6jgO3ZfagJET2hqxw-w.png" /></figure><p>Hello! This is the first half of this year’s release of Naver’s FE open-source component group <a href="https://naver.github.io/egjs/">egjs</a>.</p><p>In this release, we will introduce new features added to the <a href="https://github.com/naver/egjs-flicking">@egjs/flicking</a> component and share some tips on issues that are easy to occur when using Flicking.</p><p>— -</p><h3>🚀 New Features</h3><h4>Reactive API has been added to detect state changes in Flicking.</h4><p>Previously, when using Flicking with external design system components or customized UI, it was inconvenient to update the state on an event-driven basis by subscribing to multiple Flicking events.</p><p>Starting from the next version of Flicking, a Reactive API has been added to manage state changes reactively.</p><p>With the states provided by the Reactive API, you can update the UI based on state rather than events.</p><p>The next version of Flicking will provide the following new states:</p><ul><li>`isReachStart`: Indicates whether the first panel has been reached.</li><li>`isReachEnd`: Indicates whether the last panel has been reached.</li><li>`totalPanelCount`: The total number of panels.</li><li>`currentPanelIndex`: The index of the currently active panel.</li><li>`progress`: The scroll progress of the entire Flicking area.</li><li>`indexProgress`: The scroll progress between panels.</li></ul><p>These provided states make it easier to combine Flicking with external UI components like MUI and Ant Design.</p><p>For example, instead of using Flicking’s Pagination plugin, you can apply your desired styles to the state, like a Headless UI component, or combine it with an external design system component.</p><p>The following demo is an example of integrating MUI’s Pagination into Flicking using the Reactive API’s state. (<a href="https://naver.github.io/egjs-flicking/Demos#pagination">Demo</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*mpQBGhCl3moG3y9JV6NnfA.gif" /></figure><pre>import React from &quot;react&quot;;<br>import Flicking, { useFlickingReactiveAPI } from &quot;@egjs/react-flicking&quot;;<br>import Pagination from &quot;@mui/material/Pagination&quot;;<br>export default function PaginationExample() {<br>  const flickingRef = React.useRef(null);<br>  const {<br>    currentPanelIndex,<br>    totalPanelCount,<br>    moveTo<br>  } = useFlickingReactiveAPI(flickingRef);<br>  const handlePageChange = (event, page) =&gt; {<br>    moveTo(page - 1); // MUI Pagination은 1부터 시작<br>  };<br>  return (<br>    &lt;div&gt;<br>      &lt;Flicking ref={flickingRef}&gt;<br>        {panels.map((panel, index) =&gt; (<br>          &lt;div key={index} className=&quot;panel&quot;&gt;{panel}&lt;/div&gt;<br>        ))}<br>      &lt;/Flicking&gt;<br>      &lt;Pagination<br>        page={currentPanelIndex + 1}<br>        count={totalPanelCount}<br>        onChange={handlePageChange}<br>      /&gt;<br>    &lt;/div&gt;<br>  );<br>}</pre><p>In addition, you can implement various features using the states provided by the Reactive API.</p><p><strong>Implementation that changes the state of buttons with `isReachStart` and `isReachEnd`.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*SFSuUjV0vDnOn6VAxRbUZg.gif" /></figure><p><strong>Implementation using `progress` to show Flicking’s progress.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Pnj3rw2ajl4xGHXSQPXR6Q.gif" /></figure><p><strong>Panel transition effect using `indexProgress`, which indicates the scroll progress between panels.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*4bPiE_UsHIiM4bX5EvZ9aw.gif" /></figure><h4>Added `observePanelResize` option to track size changes of elements inside Flicking.</h4><p>Flicking has an `adaptive` option that adjusts the height of the entire area to match the height of each panel.</p><p>When this option is enabled, Flicking’s height is fixed to match the new panel whenever the currently displayed panel changes.</p><p>However, during service development, there were cases where a panel’s height could change after its content finished loading.</p><p>When Flicking and its internal panels were displayed via Server-Side Rendering, and then the panel’s internal data was fetched via Client-Side Rendering, the original Flicking could not update its height to reflect the panel’s height change because it was already fixed by the `adaptive` option.</p><p>To address such cases, the `observePanelResize` option has been added to track size changes of elements inside Flicking.</p><p>By enabling the `observePanelResize` option, the entire area’s height will be readjusted according to changes in the size of internal elements, even if Flicking’s height is fixed by the `adaptive` option.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*ykmIX_Yn62K-hOCgN0soUQ.gif" /></figure><p>The example above shows the difference in behavior when a Panel’s height changes, with and without the `observePanelResize` option enabled.</p><p>In addition to cases like the one above, this option can also prevent movement inconsistencies when a panel’s width changes during interaction with Flicking.</p><p>If a panel’s size changes in real-time due to content loading or other factors, try using the `observePanelResize` option in addition to the `adaptive` option.</p><p>— -</p><h3>🛠️ Notable Issues</h3><h4>Check your style when applying custom styles to Flicking!</h4><p>You may want to set custom styles for Flicking’s classes instead of using the default ones.</p><p>If two different services using Flicking are displayed on the same page, two Flicking instances with different styles will be rendered.</p><p>The example below shows how assigning a background color to the `flicking-camera` class of the first Flicking instance affects and breaks the style of the second Flicking instance.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XNgWCEnk3goM4wJ6_dgO9g.png" /></figure><p>Applying styles directly to Flicking’s classes like `flicking-viewport` and `flicking-camera` can affect the styles of Flicking instances in other services.</p><p>When styling Flicking’s components, we recommend scoping the styles so they apply only within a specific service’s Flicking instance, as shown in the following example.</p><pre>.service-root {<br> .flicking-viewport {<br> …<br> }<br>}</pre><p>Additionally, if you are using react-flicking, you can use the `cameraClass` option to set a custom class name for the flicking-camera element and apply styles only to that class, thereby preventing style conflicts.</p><p>— -</p><h3>📰 Service News</h3><h4>A service using JustifiedGrid’s `stretch` extension option has been released.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qglV9qupy3ruLQuf-KRhdQ.png" /></figure><p>The `stretch` option, added to <a href="https://github.com/naver/egjs-flicking">@egjs/infinitegrid</a>’s JustifiedGrid in the F<a href="https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-0dfb8d0838bf">irst Half 2024 Release</a>, is an extension option for JustifiedGrid that adjusts item widths by distorting their aspect ratios while maintaining a given height.</p><p>After performance optimizations were made to this option during the first half of 2025, an image search service using the `stretch` option was deployed for the first time.</p><p>During this process, an issue in the @egjs/imready component where the `preReady` event would not fire for rapidly loaded images was also fixed.</p><p>You can now experience the improved @egjs/infinitegrid in Naver’s search service!</p><p>— -</p><h3>🔖 egjs Releases</h3><h4><a href="https://github.com/naver/egjs-flicking">@egjs/flicking</a> 4.14.0 (2025–06–30)</h4><ul><li>Fixed an issue in React where the state was not updated when a Panel’s `className` changed.</li><li>Added the `observePanelResize` option, which detects Panel height changes and resizes the viewport when `adaptive` is true.</li><li>Fixed an issue where the input direction was incorrectly recognized after a drag in Flicking.</li><li>Fixed an issue where a resize event was triggered in an infinite loop when a Panel’s height changed.</li><li>Added `optimizeSizeUpdate` option to prevent re-rendering of Panels when the viewport is resized.</li></ul><h4><a href="https://github.com/naver/egjs-conveyer">@egjs/conveyer</a> 1.8.0 (2025–04–18)</h4><ul><li>Added `enableInput` and `disableInput` methods to enable and disable user input.</li><li>Fixed an issue where the current position was not correctly recognized after playing an animation on elements with sub-pixel widths.</li></ul><h4><a href="https://github.com/naver/egjs-axes">@egjs/axes</a> 3.9.2 (2025–06–05)</h4><ul><li>Fixed an issue in PanInput where the input direction was incorrectly recognized after a drag.</li><li>Changed PanInput so that it does not activate if there are no available input types in the `inputType` option.</li></ul><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*uc-ZJmHAIeWdTz6RPHsJ8Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e860deaef099" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/release-note-of-egjs-first-half-2025-e860deaef099">Release note of egjs(First Half 2025)</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Release note of egjs(Second Half 2024)]]></title>
            <link>https://medium.com/naver-fe-platform/release-note-of-egjs-second-half-2024-ede725e197be?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/ede725e197be</guid>
            <dc:creator><![CDATA[Malangfox]]></dc:creator>
            <pubDate>Fri, 27 Dec 2024 05:04:21 GMT</pubDate>
            <atom:updated>2024-12-27T05:04:21.458Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*KHP6jgO3ZfagJET2hqxw-w.png" /></figure><p>Hello! This is the second half of this year’s release of Naver’s FE open-source component group <a href="https://naver.github.io/egjs/">egjs</a>.</p><p>In this release, we introduce the annual usage statistics of the egjs components along with the newly added CrossFlicking feature in the Flicking component.</p><p>— -</p><h4>📈 Over 1.5 Million Downloads by the End of 2024</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*FK4b8jRL78shhqTKm93wNA.png" /></figure><p>Among various egjs components, the most popular carousel UI component <a href="https://naver.github.io/egjs-flicking/">@egjs/flicking</a> has surpassed 1.5 million <a href="https://npm-stat.com/charts.html?package=%40egjs%2Fflicking&amp;from=2017-01-01&amp;to=2024-12-17">annual downloads</a>.</p><p>We sincerely appreciate the continued interest and use of egjs components by both internal and external developers throughout 2024.</p><p>We will continue to actively incorporate user feedback and develop new features to maintain our competitiveness in the open-source ecosystem.</p><h4>🚀 New CrossFlicking Preset Added to Provide Unique UI</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*swyq9T8dhypsB7pAFpemCw.gif" /></figure><p>What if you want to create a slider where users can explore topics horizontally and view detailed content vertically?</p><p>The new content viewer added to Naver’s service has the following specifications:</p><ul><li>Horizontal slides contain topics like sports, travel, and fashion, while vertical slides contain various pieces of content for each topic.</li><li>When a user reaches the last content in a topic by sliding down, they should be able to slide down again to move to the first content of the next topic.</li><li>After moving to a new topic horizontally, the last viewed content from the previous topic should be shown when the user returns to the previous topic.</li><li>The pagination should show which slide number is currently visible in the vertical direction.</li></ul><p>Many libraries that support slider UIs, such as Swiper, Slick, and Splide, offer UIs that support only one direction (horizontal or vertical).</p><p>To support both directions, complex configurations were required, and the existing @egjs/flicking had the same issue.</p><p>Additionally, when both horizontal and vertical content movements are related, it becomes even more hard to implement this kind of UI, which requires extra implementation.</p><p>The newly added CrossFlicking feature is a solution that attempts to break the limitations of existing slider UI libraries.</p><h4>💡 New Possibilities with CrossFlicking</h4><p><strong>🛠️ Enabling Simultaneous Horizontal and Vertical Flicking</strong></p><p>When users drag using touch or mouse gestures, they rarely move perfectly horizontally or vertically. This posed a challenge as both horizontal and vertical sliders would move simultaneously.</p><p>To address this, we introduced the <a href="https://naver.github.io/egjs-flicking/Options#dragthreshold">dragThreshold</a> option, which sets the minimum distance required to detect a user’s intended drag direction, ensuring only the intended slider moves.</p><p><strong>🛠️ Simple Setup for Horizontal and Vertical Content</strong></p><p>Previously, Flicking required all panels to be passed as children elements. However, this method couldn’t distinguish between horizontal and vertical panels in a two-directional layout.</p><p>CrossFlicking offers two methods to resolve this:</p><ol><li>Group vertical panels using separate div containers.</li><li>Assign the same data-cross-groupkey attribute to panels within the same group.</li></ol><p>Users can choose the method that best suits their implementation.</p><p><strong>🛠️ New Events for Multi-Directional Flicking</strong></p><p>CrossFlicking introduces mainIndex and sideIndex properties in panel-related events, allowing developers to track horizontal and vertical progress simultaneously.</p><p>For details, check the <a href="https://naver.github.io/egjs-flicking/Presets#listening-to-events">documentation</a>.</p><h4>🔍 Try CrossFlicking from Flicking’s Presets</h4><p>Without additional plugins or configurations, CrossFlicking enables multi-directional UI. It is categorized as a Preset for simplified implementation.</p><p>CrossFlicking supports all methods and events from Flicking, excluding methods like <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#append">append</a>, <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#prepend">prepend</a>, <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#insert">insert</a>, and <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#remove">remove</a>.</p><p><strong>Fixed Options in CrossFlicking</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0zkGie9B13QdA1y0q2hV2Q.png" /></figure><p>Visit the <a href="https://naver.github.io/egjs-flicking/Presets">demo page</a> to explore CrossFlicking in action.</p><h4>🎉 InfiniteGrid Featured on JSWeekly!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHmRLOr-BJxoIfo67zP4Ng.png" /></figure><p>The JavaScript newsletter <a href="https://javascriptweekly.com/issues/697#:~:text=InfiniteGrid%204.12:%20Arrange%20Card%20Elements%20Infinitely%20in%20a%20Grid%20Layout">JSWeekly</a> has featured <a href="https://naver.github.io/egjs-infinitegrid/">@egjs/infinitegrid</a>!</p><p>InfiniteGrid is a component that arranges card-style UI elements in various layouts while adding infinite scrolling functionality.</p><p>It offers extensive customization options through various settings and events and supports performance optimization by dynamically adding or removing content based on the current scroll position.</p><p>If you’re looking to create an infinite scroll UI for applications like photo galleries or shopping product lists that need to load large amounts of data in real time, give @egjs/infinitegrid a try.</p><p>If you’re already using InfiniteGrid, you can enhance user experience with the stretch feature added to the JustifiedGrid layout in the <a href="http://medium.com/naver-fe-platform/release-note-of-egjs-first-half-2024-ee2d531ecc03?source=collection_home---4------3-----------------------">first-half 2024 release</a>.</p><h4>🔖 egjs Releases</h4><h4><a href="https://naver.github.io/egjs-flicking/">@egjs/flicking</a> 4.12.0 (2024–12–12)</h4><ul><li>Added a new preset [CrossFlicking](<a href="https://naver.github.io/egjs-flicking/ko/Presets">https://naver.github.io/egjs-flicking/ko/Presets</a>)</li><li>Fixed an error that disabled flicking blocks native scroll.</li><li>Fixed an error that panels disappear when resizing with the `renderOnlyVisible` option enabled.</li><li>Fixed an error where the initial Panel is set to the last Panel when `display: none` is applied to the viewport.</li></ul><h4><a href="https://naver.github.io/egjs-agent/">@egjs/agent</a> 2.4.4 (2024–08–23)</h4><ul><li>Added logic to handle cases where OS related data is not available.</li></ul><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*uc-ZJmHAIeWdTz6RPHsJ8Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ede725e197be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/release-note-of-egjs-second-half-2024-ede725e197be">Release note of egjs(Second Half 2024)</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[egjs 2024년 하반기 릴리즈 소식을 전해드립니다]]></title>
            <link>https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%ED%95%98%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-d02bf64d6cf6?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/d02bf64d6cf6</guid>
            <dc:creator><![CDATA[Malangfox]]></dc:creator>
            <pubDate>Fri, 27 Dec 2024 05:04:07 GMT</pubDate>
            <atom:updated>2024-12-27T05:04:07.874Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*KHP6jgO3ZfagJET2hqxw-w.png" /></figure><p>네이버의 FE 오픈소스 컴포넌트 그룹인 <a href="https://naver.github.io/egjs/">egjs</a>의 24년 상반기 릴리즈 소식을 전해드립니다.</p><p>이번 정기 릴리즈에서는 egjs 컴포넌트들의 연간 사용량 통계와 함께 Flicking 컴포넌트에 새로 추가된 CrossFlicking 기능을 소개합니다.</p><p>— -</p><h4>📈 2024년이 지나며 150만을 넘어섰습니다.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/534/1*FK4b8jRL78shhqTKm93wNA.png" /></figure><p>​egjs의 다양한 컴포넌트들 중에서도 가장 큰 인기를 누리고 있는 캐러셀 UI 컴포넌트 <a href="https://naver.github.io/egjs-flicking/">@egjs/flicking</a>의 <a href="https://npm-stat.com/charts.html?package=%40egjs%2Fflicking&amp;from=2017-01-01&amp;to=2024-12-17">연간 다운로드 수</a>가 150만회를 넘었습니다.​</p><p>2024년에도 egjs 컴포넌트에 대한 지속적인 관심과 사용에 사내 및 사외의 개발자분들께 깊은 감사의 마음을 전합니다.​</p><p>앞으로도 오픈 소스 생태계에서의 경쟁력을 이어나갈 수 있도록 사용자 피드백을 적극 반영해나가고 새로운 기능을 지속적으로 개발해나갈 수 있도록 하겠습니다.</p><h4>🚀 특별하고 고유한 전방향 스와이프 UI를 제공하는 CrossFlicking 기능이 추가되었습니다.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/440/1*swyq9T8dhypsB7pAFpemCw.gif" /></figure><p>사용자가 좌우 방향으로 주제를 탐색하고, 상하 방향으로 해당 주제의 세부 컨텐츠를 살펴보는 슬라이더를 만들고 싶다면 어떻게 해야 할까요?</p><p>네이버 통합 검색에 새로 추가될 숏텐츠 뷰어는 다음과 같은 스펙을 가졌습니다.</p><ul><li>가로 방향 슬라이드로는 스포츠, 여행, 패션 등 주제들이 존재하고 세로 방향 슬라이드로는 각 주제별로 여러 컨텐츠들이 존재합니다.</li><li>하나의 주제에서 아래 방향으로 끝까지 슬라이드해서 마지막 컨텐츠에 도착했을 때 한 번 더 아래 슬라이드를 통해 다음 주제의 첫 번째 컨텐츠로 넘어가야 합니다.</li><li>가로 방향으로 움직여 다른 주제로 넘어간 뒤 이전 주제로 돌아갈 때 이전 주제에서 마지막으로 보고 있던 컨텐츠가 노출되어야 합니다.</li><li>현재 세로 방향 슬라이드 중 몇 번째 슬라이드가 화면에 표시되고 있는지 페이지네이션을 통해 알 수 있어야 합니다.​</li></ul><p>Swiper, Slick, Splide 등 슬라이더 UI를 지원하는 여러 라이브러리들은 가로 또는 세로 방향 중 하나의 축으로만 된 UI를 제공합니다.​</p><p>그래서 두 방향을 모두 지원하기 위해서는 복잡한 설정이 필요했고, 기존의 @egjs/flicking 또한 같은 문제를 안고 있었습니다.​</p><p>그뿐만 아니라 위처럼 좌우 방향의 컨텐츠 이동과 상하 방향의 컨텐츠 이동이 연관성을 가져 추가적인 스펙이 존재하는 UI의 경우 이를 구현하기 위해 많은 노력이 필요했습니다.​</p><p>이번에 추가된 기능 CrossFlicking은 이처럼 기존 슬라이더 UI를 지원하는 라이브러리들이 가진 제약 사항을 타파하기 위한 시도에서 출발했습니다.</p><p><strong>​</strong></p><h4>💡 CrossFlicking 개발 비화, 그리고 새로 가능해진 것들</h4><h4><strong>​</strong></h4><p><strong>🛠️ 수직 및 수평 방향으로 동시에 이동이 가능해집니다.</strong>​</p><p>마우스나 터치를 통해 드래그 제스쳐를 할 때 정확하게 수평 방향으로 움직이거나 정확하게 수직 방향으로 움직이는 경우는 극히 드뭅니다.​</p><p>모든 방향으로 스와이프할 수 있는 슬라이더 UI를 처음으로 구현했을 때 마주한 문제로 사용자의 제스쳐로 수직 방향과 수평 방향의 슬라이더가 항상 같이 움직이는 현상이 있었습니다.​</p><p>이 문제를 해결하기 위해서는 사용자가 어떤 방향으로 드래그하려 했는지에 대한 의도를 파악해서 해당 방향의 슬라이더만 움직이게 해야 할 필요가 있었고, 이를 위해 사용자의 드래그 제스쳐 인식에 필요한 최소 거리를 나타내는 <a href="https://naver.github.io/egjs-flicking/Options#dragthreshold">dragThreshold</a> 옵션을 추가했습니다.​</p><p>해당 옵션을 설정하는 것으로 사용자가 어느 정도의 거리를 가로 또는 세로 방향으로 드래그해야 사용자의 제스쳐를 인식하고 그 방향의 슬라이더만을 움직이게 설정할 수 있도록 설계했습니다.​</p><p><strong>🛠️ 간단하게 가로 방향의 컨텐츠와 세로 방향의 컨텐츠를 설정할 수 있습니다.</strong>​</p><p>한 가지 방향만을 지원하는 Flicking을 사용할 때는 Flicking 인스턴스에 전달할 엘리먼트의 children으로 스와이프되는 전체 항목들, 패널을 전달할 수 있었습니다.​</p><p>그러나 두 가지 방향으로 패널을 배치하게 되면서 기존의 방법만으로는 가로 방향과 세로 방향의 패널을 구분할 수 없게 되었습니다.</p><p>이 문제를 해결하기 위해 CrossFlicking에서는 두 가지 사용 방법을 제공하기로 했습니다.</p><p>첫 번째 방법으로 세로 방향으로 움직일 패널들을 그룹 단위로 분리해서 여러 div로 전달하는 방법을 제공하며,​</p><p>두 번째 방법으로는 패널 엘리먼트마다 “data-cross-groupkey” 어트리뷰트를 설정해서 같은 값을 가진 패널끼리 같은 그룹으로 분리하는 방법을 마련했습니다.​</p><p>사용자는 두 가지 방법 중 구현이 편리한 방법을 선택해서 사용할 수 있습니다.​</p><p><strong>🛠️ 전방향 조작을 위한 새로운 이벤트들을 추가했습니다.​</strong></p><p>기존의 Flicking 인스턴스에서는 가로 방향과 세로 방향 중 설정된 방향으로만 이벤트들을 제공했습니다.​</p><p>CrossFlicking이 쓰이는 곳에서는 가로 방향의 진행도와 세로 방향의 진행도를 모두 확인할 수 있어야 하는데, 컴포넌트에서 발생하는 이벤트로 이 정보들을 알 수 있어야 합니다.​</p><p>CrossFlicking에서는 기존에 존재하는 패널 관련 이벤트를 확장해서 가로 방향의 상태 mainIndex와 세로 방향의 상태 sideIndex라는 속성을 추가하는 방법으로 기존 Flicking의 이벤트만으로는 구현이 어려웠던 부분을 개선했습니다.​</p><p>CrossFlicking의 <a href="https://naver.github.io/egjs-flicking/Presets#listening-to-events">문서 페이지</a>에서 새로 추가된 이벤트들의 사용 방법이 소개되어 있습니다.</p><p>​</p><h4>🔍 이제 Flicking의 Preset에서 CrossFlicking을 만나보세요.<strong>​</strong></h4><p>추가적인 플러그인이나 복잡한 설정 없이 CrossFlicking 하나만으로 가로와 세로 축을 모두 활용하는 UI를 만들 수 있습니다.​</p><p>CrossFlicking은 기존에 복잡한 구현이 필요했던 UI를 간편하게 사용할 수 있도록 하는 Preset이라는 분류로 추가되었습니다.​</p><p>CrossFlicking에서는 기존 Flicking의 메서드들 중 Panel을 조작하는 <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#append">append</a>, <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#prepend">prepend</a>, <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#insert">insert</a>, <a href="https://naver.github.io/egjs-flicking/ko/docs/api/Flicking#remove">remove</a> 메서드를 제외한 모든 메서드와 이벤트를 사용할 수 있으며, 아래의 옵션들을 제외한 기존의 옵션들을 사용할 수 있습니다.​</p><p><strong>기존 옵션 중 고정값이 사용되는 옵션 목록</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nAIOXsZSRI7PaQAElDyeZQ.png" /></figure><p><a href="https://naver.github.io/egjs-flicking/Presets">데모 페이지</a>에서 새로 추가된 CrossFlicking 기능의 사용 방법과 적용 예시를 확인해볼 수 있습니다.</p><p>​​</p><h4>🎉 InfiniteGrid가 JSWeekly에 소개되었습니다!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OHmRLOr-BJxoIfo67zP4Ng.png" /></figure><p>여러 프로젝트들을 소개하는 JavaScript 뉴스레터 <a href="https://javascriptweekly.com/issues/697#:~:text=InfiniteGrid%204.12:%20Arrange%20Card%20Elements%20Infinitely%20in%20a%20Grid%20Layout">JSWeekly</a>에서 <a href="https://naver.github.io/egjs-infinitegrid/">@egjs/infinitegrid</a>가 소개되었습니다.​</p><p>InfiniteGrid는 카드형 UI를 여러 가지 형태의 레이아웃으로 배치하는 동시에 무한 스크롤 기능을 더한 컴포넌트입니다.​</p><p>InfiniteGrid는 다양한 옵션과 이벤트를 통해 커스터마이징이 가능하며, 현재 스크롤 위치에 따라 동적으로 콘텐츠를 추가 및 제거하는 성능 최적화 또한 지원합니다.​</p><p>사진 갤러리나 쇼핑 상품 리스트처럼 많은 데이터를 실시간으로 불러오는 무한 스크롤 UI를 만들고자 한다면 @egjs/infinitegrid를 사용해보세요.​</p><p>기존에 이미 InfiniteGrid를 사용 중이라면 <a href="https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-0dfb8d0838bf">2024년 상반기 릴리즈</a>와 함께 InfiniteGrid의 JustifiedGrid 레이아웃에 추가된 stretch 기능으로 개선된 사용자 경험을 제공할 수 있습니다.</p><h4>🔖 egjs 릴리즈 내역</h4><h4><a href="https://naver.github.io/egjs-flicking/">@egjs/flicking</a> 4.12.0 (2024–12–12)</h4><ul><li>전방향으로 슬라이드 가능한 UI를 제공하는 CrossFlicking 기능이 추가되었습니다.</li><li>disable 상태인 Flicking 영역을 드래그할 때 브라우저의 스크롤이 작동하지 않던 현상을 수정했습니다.</li><li>renderOnlyVisible 옵션을 사용 중일 때 resize를 빈번하게 발생시키면 Panel이 사라지던 현상을 수정했습니다.</li><li>Flicking이 초기화될 때 display: none 등으로 Panel들이 보이지 않는 경우 초기 인덱스가 마지막 Panel이 되던 현상을 수정했습니다.​</li></ul><h4><a href="https://naver.github.io/egjs-agent/">@egjs/agent</a> 2.4.4 (2024–08–23)</h4><ul><li>OS 관련 데이터가 넘어오지 않은 경우에 대한 대응 로직이 추가되었습니다.</li></ul><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*uc-ZJmHAIeWdTz6RPHsJ8Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d02bf64d6cf6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%ED%95%98%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-d02bf64d6cf6">egjs 2024년 하반기 릴리즈 소식을 전해드립니다</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Performance of NAVER Search — Data Collection and Visualization]]></title>
            <link>https://medium.com/naver-fe-platform/web-performance-of-naver-search-data-collection-and-visualization-e349445870a7?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/e349445870a7</guid>
            <dc:creator><![CDATA[최진우]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 05:09:13 GMT</pubDate>
            <atom:updated>2024-10-16T05:09:13.616Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Performance of NAVER Search — Data Collection and Visualization</h3><p><em>이 글은 네이버 기술 블로그 D2 의 “</em><a href="https://d2.naver.com/helloworld/9227596">네이버 통합 검색의 웹 성능 — 데이터 수집과 시각화</a><em>” 을 영문 번역한 글입니다.</em></p><p>What is your first thought when you think of the performance of NAVER Search? It could be how exactly search results match your intention, how quickly they are displayed, or how interestingly you can explore them. All of these perspectives can represent the performance of NAVER Search.</p><p>The series of “Web Performance of NAVER Search” will cover what web performance is in NAVER Search and how to improve it. In this first article, you will learn about data collection to measure the web performance of NAVER Search and visualization of web performance.</p><h3><strong>Web performance and web vitals</strong></h3><p>There are many web services, each with its own features and values. No matter what type of web services you use, you may have the following common experiences as long as those services run on a web platform.</p><p><em> 1. Use your browser to visit a web page.</em></p><p><em> 2. Wait for the page content to be displayed.</em></p><p><em> 3. Click or scroll the page to use the service.</em></p><p>Apart from the service itself, these user experiences associated with a web platform are called web performance.</p><p>You may have negative experiences regarding web performance. For example, content may load too slowly when you open a web page, or you may be unable to click a specific component on the web page that you think has fully loaded but actually has not. In such cases, the service will likely gain a poor reputation no matter how great its features or content is. This is why maintaining web performance is essential to delivering the features and values of a web service.</p><p>Then, how can you do that? The simplest way is to measure and control web performance metrics. Web vitals are a set of quantitative metrics for web performance, which includes Largest Contentful Paint (LCP), Interaction to Next Paint (INP), Cumulative Layout Shift (CLS), and First Contentful Paint (FCP).</p><p> <em>LCP: Measures how quickly the largest image or text block loads.</em></p><p><em> INP: Measures how quickly a website responds to user interactions.</em></p><p><em> CLS: Measures how much visible content has unexpectedly shifted.</em></p><p><em> FCP: Measures the time it takes for the first piece of content to appear on a web page.</em></p><p>As a web service, it is important for NAVER Search to properly maintain and control its web performance. For this, we have measured and collected web vitals, including LCP, FCP, and INP, of NAVER Search result pages, and configured a dashboard to visualize them.</p><p>In this article, I will discuss the entire process of collecting and visualizing one of the web vitals, LCP.</p><h3>Lab data and field data</h3><p><a href="https://github.com/GoogleChrome/lighthouse">Lighthouse</a> is a tool that measures web vitals. It helps you measure the web vitals score of the current page and provides advice on how to improve its performance. You might assume that it would be easy to measure the web performance of NAVER Search result pages using Lighthouse, but actually it is not. To understand why Lighthouse is not a suitable tool, you need to understand the difference between lab data and field data.</p><p><strong>Lab data</strong></p><p>Lab data refers to the data measured in a controlled environment where specific conditions are fixed. One good example of lab data is performance metrics measured using a program like Lighthouse in a specific physical environment such as a local computer. The following web performance data measured using Lighthouse does not represent the actual web performance status of NAVER Search result pages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*nfWIYjKGu_Qz2-6EKXt1OQ.png" /></figure><p><strong>Field data</strong></p><p>Field data, on the contrary, refers to the data measured directly in a real user environment. NAVER Search basically has a tremendous amount of users, meaning there is a variety of user environments. And NAVER Search result pages show different content and layouts based on what is searched for, when the search is done, or who does the search. This makes LCP elements quite variable. In the following figure, LCP elements on each page are marked in orange box.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*ozMjM_0PGQ97lg5lCwLLBw.png" /></figure><p>After all, it is not realistically possible to measure lab data for all combinations of user environments and page layouts. Collecting field data is required, therefore, to understand the web performance status of NAVER Search.</p><h3>Measure and collect field data</h3><p>You can measure and collect the field data of NAVER Search result pages, using the script that loads when users enter a search results page. The script determines which element is considered for LCP on the current search results page and measures LCP, using the <a href="https://github.com/GoogleChrome/web-vitals">web-vitals</a> library . Then, it passes the measured data to the log collection system, using the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Navigator/sendBeacon">sendBeacon() method</a> of the <a href="https://developer.mozilla.org/en-US/docs/Web/API/Beacon_API">Beacon API</a>.</p><p>The sendBeacon() method is called when the visibility state of the current page changes, which is, for example, when the user closes the page, clicks the Back button, or repeats the search with another search term.</p><p>This can reduce network costs. Since the time required to measure each web vital varies, the script is designed to wait until all web vitals are measured and then send the data at once to reduce network costs. It does not resend the data from the same page to prevent duplicate data from being collected whenever the visibility state of the page changes. So, only one type of field data is collected for one search results page.</p><p>Handling the measured data when the page’s visibility state is hidden is another problem. The browser renders the page with hidden visibility later than others, resulting in poor LCP. The larger the amount of such data, the more it affects the overall statistics. Fortunately, the number of pages with hidden visibility was low (0.03%), so we decided to collect all data without any filtering.</p><p>Yet, there is still a possibility that bad data may be collected. For example, if a page’s visibility state changes as the user leaves the page before the content is fully rendered, LCP may be measured during the rendering of the page. This comes from how the web-vitals library works to identify an element considered for LCP. The library does not identify it at once after the final page is rendered, but keeps updating it whenever a larger element appears during the rendering to measure LCP. If the user leaves the page before it is fully rendered, LCP at that point is measured, which may vary even for the same page in the same user environment.</p><p>The measurement of LCP is also affected by the supported environments for the web-vitals library and Beacon API. The web-vitals library is available only in browsers (mostly Chromium-based) that support the web API for measuring web vitals. Moreover, the Beacon API is not available in Internet Explorer. This is why most field data is currently collected from Chromium-based browsers.</p><h3>Web performance core metrics</h3><p>Web vitals field data has started to be collected in the way previously mentioned. The next thing to do was to choose the core metric that can represent the web performance of NAVER Search and to decide how to manage it. The following three criteria were used to choose the core metric.</p><p> 1. <em>A quantitative metric whose values can be compared and whose threshold can be set.</em></p><p><em> 2. A metric that can detect both the server-side and the client-side performance.</em></p><p><em> 3. A metric for which changes in values can be detected and the causes of the changes can be analyzed.</em></p><p>Based on these criteria, LCP was chosen as the core metric for the web performance of NAVER Search. LCP is a quantitative metric that measures both the server-side performance (response time) and the client-side performance (perceived page load speed). It was also expected that we could use additional data to analyze the causes of changes in LCP values.</p><p>Then, we needed to lay down guidelines on how to maintain LCP scores. We referred to <a href="https://web.dev/articles/defining-core-web-vitals-thresholds">Defining the Core Web Vitals metrics thresholds</a>, the LCP guidelines suggested by Google. According to Google’s guidelines, a site is classified as “GOOD” if the 75th percentile (p75) LCP of all users is 2.5 seconds or less, “NEED IMPROVEMENT” if it is greater than 2.5 seconds and less than or equal to 4 seconds, and “POOR” if it is greater than 4 seconds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*agidmsHJC5tfhRgSDvbUyA.png" /></figure><p>For NAVER Search, we decided to adopt stricter criteria than Google: a site is classified as “GOOD” if the p95 LCP of all users and the p75 LCP of content specific aggregates are 2.5 seconds or less, “NEED IMPROVEMENT” if they are greater than 2.5 seconds and less than or equal to 4 seconds, and “POOR” if they are greater than 4 seconds. Here, “content specific aggregates” refer to the data aggregated when specific content is measured for LCP. The reason why we added content specific aggregates, unlike Google, was to manage changes in LCP of specific content.</p><h3><strong>Web performance dashboard</strong></h3><p>After the core metric and necessary guidelines were determined, we started to develop a dashboard page where you can view and monitor the performance data of NAVER Search. The dashboard consists of the following two pages:</p><ul><li><em>Real-time page: For analyzing and monitoring real-time performance.</em></li><li><em>Details page: For analyzing data when an issue occurs</em></li></ul><p><strong>Real-time page</strong></p><p>The real-time page was designed to show the p95 LCP of all data collected for a specified period of time and the p75 LCP of content specific aggregates. For example, let’s say a total of 500 cases of search results have been displayed for the last 24 hours, which include 200 cases of people content considered for LCP, 150 cases of place content considered for LCP, and 150 cases of blog content considered for LCP. Then, the real-time page will show the p95 LCP of 500 cases, and the p75 LCP of 200 cases of people content, of 150 cases of place content, and of 150 cases of blog content, respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*jRZ0By4CwcEkkNvdrK0B8A.png" /></figure><p><strong>Details page</strong></p><p>The details page helps you analyze sudden changes in LCP to understand the reasons behind them. For this, it provides a histogram showing changes in LCP distribution, and time-series graphs illustrating changes in LCP, in server response time to understand the influence of the server, and data count changes to detect issues related to data collection or a surge in searches. It also shows the p50 LCP and a moving average besides the core metrics, the p95 and p75 LCP on the time-series graph of LCP to help you easily understand tendencies or changes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*nb9T3j0LvpdBm9j_E1ME3g.png" /></figure><h3>Conclusion</h3><p>We have measured and collected web vitals and implemented a dashboard to understand the web performance status of NAVER Search. However, what is important is to move to the next step, which involves constantly maintaining and controlling the web performance based on the data we have learned. The next article will cover how to monitor the web performance of NAVER Search and the efforts made to improve it.</p><h3>Web performance of NAVER Search Series</h3><ul><li>Web Performance of NAVER Search — Data Collection and Visualization</li><li>Web Performance of NAVER Search — Monitoring and Performance Improvement</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e349445870a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/web-performance-of-naver-search-data-collection-and-visualization-e349445870a7">Web Performance of NAVER Search — Data Collection and Visualization</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web Performance of NAVER Search — Monitoring and Performance Improvement]]></title>
            <link>https://medium.com/naver-fe-platform/web-performance-of-naver-search-monitoring-and-performance-improvement-8db383bf1462?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/8db383bf1462</guid>
            <category><![CDATA[performance-monitoring]]></category>
            <category><![CDATA[frontend-performance]]></category>
            <category><![CDATA[naver-search]]></category>
            <category><![CDATA[lcp]]></category>
            <dc:creator><![CDATA[brown10987]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 05:09:11 GMT</pubDate>
            <atom:updated>2024-10-16T05:09:11.901Z</atom:updated>
            <content:encoded><![CDATA[<h3>Web Performance of NAVER Search — Monitoring and Performance Improvement</h3><p><em>이 글은 네이버 기술 블로그 D2 의 “</em><a href="https://d2.naver.com/helloworld/8113611"><em>네이버 통합 검색의 웹 성능 — 모니터링과 성능 개선</em></a><em>” 을 영문 번역한 글입니다.</em></p><p>In the first article of the “Web Performance of NAVER Search” series, “Web Performance of NAVER Search — Data Collection and Visualization,” I have discussed how to collect data to measure the web performance of NAVER Search and the dashboard that visualizes the collected data.</p><p>In this second article of the series, I will show you how to view the web performance status on the dashboard and what has been attempted to improve the web performance of NAVER Search.</p><h3><strong>Performance monitoring</strong></h3><p>NAVER Search employs two methods to constantly monitor its web performance: one is using performance reports to check performance changes on a regular basis, and the other is using a performance notification system to quickly detect and respond to web performance issues.</p><h4><strong>Performance reports</strong></h4><p>In NAVER Search, the following performance reports are automatically generated on a weekly and monthly basis, helping you monitor the current web performance status and track changes compared to the previous week or month based on various types of collected data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*hYvOTAtN8SFaKfmKyQDYRA.png" /></figure><p>The performance reports page shows the web performance of content areas frequently exposed to users as well as that of all the search results pages, which gives you a more accurate picture. For example, a performance issue regarding a specific content area may or may not affect the entire performance graph, depending on the exposure frequency and Largest Contentful Paint (LCP) distribution of the area. This is why it is essential to consistently monitor the web performance of major content areas as well as the overall web performance.</p><p>The page also helps you easily figure out how web performance changes compared to the previous period. It is highly likely that web performance issues may occur especially before or after a deployment, so the page is designed to show performance changes at the point of deployment.</p><p>We once detected web performance changes at deployment time and fixed the problem. After a deployment, LCP used to temporarily worsen and then recover over time as in the following figure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*cgFDRY48Dxz01eNRTt8U5w.png" /></figure><p>This was hardly recognized before the implementation of performance reports, which helped us discover that the problem occurs whenever a specific JavaScript file is deployed. This JavaScript file contained relatively complicated logic, and users had to download the file again upon deployment, causing web performance to temporarily deteriorate. Although it was a temporary phenomenon, users might experience slower loading of web pages. To fix the problem, we separated the JavaScript file into several smaller files. This way, performance reports can help you directly find out performance changes when an event occurs and identify a problem based on them.</p><p>When the performance reports page was first provided, however, we received the following feedback.</p><ul><li>I didn’t know that this page even exists.</li><li>I don’t know what I can get from or what I can do with this page.</li></ul><p>Reflecting the feedback, the performance representative began analyzing automatically generated performance reports and providing analysis data via email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*_BEcv6TtOERXwweH-d02LQ.png" /></figure><p>It was a hassle to analyze and summarize performance reports in every detail at first, but the entire process eventually settled down and became automated. In addition, the analysis data provided by the performance representative made it easy for recipients to understand web performance and increased their interest in the web performance of the content areas they were responsible for.</p><h4><strong>Performance notifications</strong></h4><p>What bothered us most regarding monitoring web performance was how to respond to web performance issues. After many trials and errors to quickly detect performance issues and pinpoint the causes of them, we employed a performance notification system. Performance notifications can help:</p><ul><li>Quickly detect performance issues</li><li>Quickly pinpoint the causes of performance issues</li></ul><p>The performance reports previously mentioned are useful for tracking web performance changes, but not for quickly detecting performance issues. So, we started checking performance changes every minute based on real-time data. The logic to do this was easy to implement, but we encountered a problem where notifications were often generated unexpectedly due to irregular minutely performance fluctuations, which were not actual errors.</p><p>To resolve this problem, we changed the way to track web performance changes from value-based to section-based: the former simply compares the current web performance data with that a minute ago, while the latter compares the web performance data for the recent 3 minutes with that for the previous 5 minutes, after analyzing patterns of web performance issues. And we set a threshold based on the analyzed patterns so that notifications were sent only when the threshold was reached.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*gKxqf1bn_E5d7R_j0WGFkA.png" /></figure><p>This new logic made it easy to quickly detect web performance changes. Yet, we needed to determine why performance notifications were generated each time, which took quite a long time. After going through such a process many times, we discovered that there is certain data that should be checked whenever a web performance issue occurs. So, we decided to automate this to provide information that helps you quickly determine the causes of performance notifications.</p><p>When an LCP change is detected, you should first check your server response time. LCP is highly responsive to server response time, which can thus be used to determine if the change was caused by a server. If the server response time changed, additional details should be considered, such as which section of the entire server response time changed, and whether a timeout occurred on a specific server.</p><p>If a performance issue occurred without a change in server response time, it could be caused by the client’s performance change. This can usually happen when a deployment is run, because it is highly unlikely that the web performance of many users temporarily changes although the client’s logic does not change.</p><p>It is also helpful to check changes in search terms or in the number of logs. It is not unusual for NAVER Search to show a surge in the number of searches for a specific search term. In this case, a specific search results page is exposed more often than usual, causing the entire performance to change temporarily. For example, if the number of searches for earthquake-related search terms increases after an earthquake, a map showing earthquake zones is included in the search results. This area shows poorer LCP than other areas, resulting in degradation of the total LCP.</p><p>Like this, some parts of the data analysis process were automated to send a notification email as shown in the following figure when a performance issue occurs. The notification system still has things to advance but can help quickly detect and respond to performance issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/678/1*w6lRcF2WH0F3uM2A7SMkQQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/1*31Mhk31kJlGL7VC055IRmw.png" /></figure><h3><strong>Web performance improvements</strong></h3><p>As you can see in the performance reports page in [[ (p.)]], NAVER Search was not always compliant to the web performance guidelines in 2023. A bar marked in yellow in the following chart is the section that needs your attention because the web performance guidelines are not kept to. The monitoring system helps you recognize the point of time when web performance should be improved.</p><p>Moreover, NAVER Search increasingly requires richer and more advanced features to provide the best search results. Such new features are highly likely to run slowly, causing users to experience longer response time. This is another reason to maintain and control performance.</p><p>Web performance is not usually noticeable, but it can severely affect your business when users perceive it. Here are some cases where web performance is proven to be an important factor in running a web service.</p><ul><li><a href="https://ai.googleblog.com/2009/06/speed-matters.html">Speed Matters</a>: The longer users were exposed to poor web performance, the fewer they did searches.</li><li><a href="https://developers.google.com/search/blog/2021/04/vodafone-case-study?hl=en">Vodafone: A 31% improvement in LCP increased sales by 8%</a>: Improved LCP led to more sales.</li><li>Modern Metrics: Slower LCP led to more rage clicks.</li></ul><p>Here is one of several attempts we have made to improve the web performance of NAVER Search.</p><h4><strong>Previous way</strong></h4><p>In NAVER Search, search results consist of several search areas, each of which is run independently and requires different logic (JavaScript). Previously, the JavaScript code loaded when the DOM of the search results page was fully rendered and the onLoad event of the browser occurred. More specifically, it loaded 50 ms after the onLoad event occurred.</p><p>The following figure illustrates how search results are rendered.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Xsq_74OXgItCLMTsSzaHEw.png" /></figure><p>One benefit of loading the JavaScript code based on the occurrence of the onLoad event is that it makes the event occur earlier. It sounds a little strange, but the onLoad event of the browser occurs once all the resources on the page have loaded, where the resources include images, CSS, JavaScript, etc. If the JavaScript code is set to load after the onLoad event occurs, the event occurs when all the resources except the JavaScript code have loaded. That is, the onLoad event occurs as early as the JavaScript load time.</p><p>Then why is it beneficial to make the onLoad event occur earlier?</p><p>There are two reasons: One reason is to show users the search results page more quickly. The browser stops rendering while running the JavaScript logic. Thus, running the JavaScript code before rendering is complete results in delayed loading of the search results page. This is why NAVER Search is designed to load the JavaScript code after the onLoad event occurs for better web performance.</p><p>The other reason is to improve web performance metrics. Before LCP was adopted as the web performance metric for NAVER Search, when the onLoad event occurs was an important web performance metric. As mentioned earlier, the onLoad event occurs when all the resources have loaded, which is the time when users are able to do searches. This means that user experience can be affected if a problem with loading a specific resource makes the onLoad event occur later than usual. Various attempts were made to make the onLoad event occur earlier, one of which was setting the JavaScript code to load after the event occurs. This can actually make the onLoad event to occur earlier, but the perceived load speed is unlikely to change as expected.</p><h4><strong>Problems with the previous way</strong></h4><p>For the reasons previously mentioned, the JavaScript code was set to load after the onLoad event occurs. However, there are two problems here:</p><p>First, the later the JavaScript code loads, the poorer the LCP score is. In the figure that illustrates how search results are rendered in NAVER Search, there are three different points of time measured for LCP.</p><ol><li>When a text area is considered for LCP</li></ol><p>2. When an image area is considered for LCP</p><p>3. When an area rendered with JavaScript is considered for LCP</p><p>If the JavaScript code loads later, the third one will show a poor LCP score. This usually happens when a map appears on the page.</p><p>Second, if the onLoad event occurs later, the JavaScript code will also load later. This can affect usability rather than web performance. What if it takes too long to download a resource such as an image or CSS that is used to display search results? The onLoad event does not occur until the resource download is complete, resulting in the delayed loading of JavaScript code. Users can view the page except the resource, but will not be able to do what they expect as the JavaScript code does not load yet.</p><p>In spite of this problem, it was not easy to change when the JavaScript code loads because we should keep the previous web performance metric, the time when the onLoad event occurs, good. It was also hard to expect how the changed loading of JavaScript code affects user experience. Fortunately, we prepared a system that can determine the impact on users by analyzing the new web performance metric, LCP, and error logs, so we decided to change the loading of JavaScript code.</p><h4><strong>Resolution</strong></h4><p>In order to fix the problem with loading the JavaScript code after the onLoad event occurs and not to affect the previous search results, the timely loading of JavaScript code was expected to be after the DomContentLoaded event (hereinafter, “the DCL event”) occurs.</p><p>The DCL event occurs after your browser completely parses HTML into a DOM tree. This means that it usually occurs earlier than the onLoad event because whether the DOM is complete can be determined regardless of whether other resources load. Therefore, it seemed that loading the JavaScript code after the DCL event occurs could fix the previous problems.</p><p>Above all, this can address the problem where the later the JavaScript code loads, the poorer the LCP score is. As the JavaScript code loads earlier based on the occurrence of the DCL event, rather than the onLoad event, the LCP score of the area rendered with the JavaScript logic will get better.</p><p>This method can also resolve the problem where the later the onLoad event occurs, the later the JavaScript code loads. Since the DCL event occurs regardless of the loading of other resources, a problem with loading a specific resource does not affect the loading of JavaScript code for searches.</p><p>It seemed simple, but we needed to ensure that changing the logic to work based on the DCL event, rather than the onLoad event, causes no issues. So, we decided to take the time to run A/B tests for service stability. The following figure shows experimental groups and control groups for A/B tests.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*a0Ci28W-CgW1z5XHp4B1UQ.png" /></figure><p>There are three major experimental groups: T1, T3, and T5. For each experimental group, we set different delays after the occurrence of DCL event to check what happens when the JavaScript code loads. Of course, loading without any delays was expected to be good in web performance, but we needed to check if there is any problem with loading large JavaScript code at the point of a major event in the browser.</p><h4><strong>A/B test results</strong></h4><p>The following graph shows the results of A/B tests conducted over nearly one month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*F2YPzF3Cdww5nWtfSnZPyQ.png" /></figure><p>In terms of web performance, the earlier the JavaScript code loaded, the better the LCP scores, as expected. Compared with the control groups working based on the onLoad event, the LCP values (based on the 95th percentile) of the experimental groups working based on the DCL event were improved by about 100 ms (4~5%). When comparing the experimental groups with different delays with each other, the LCP values were different by only about 5~10 ms, although the one with no delay had the lowest LCP values. We also found that the areas with improved web performance showed an increase in the number of clicks and in click quality based on the analyzed results of business metrics.</p><p>Improved performance was already expected, so we tried to make sure that there was any problem. There is one thing unusual when you look at the number of errors for each experimental group. The experimental groups loading the JavaScript code based on the occurrence of the DCL event showed relatively high error counts, more specifically 10~15% more errors, than others. We found that more errors occurred when the RequireJS logic was run. It seemed that various types of logic might run based on the DCL event, one of the major events in the browser, causing timing issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*oGvVPNdp8tSkRMlaIHb45A.png" /></figure><p>It was not easy to immediately fix those errors at that time, so we decided to record error logs more intensively and load the JavaScript code 30 ms after the DCL event occurs.</p><h4><strong>Improved web performance</strong></h4><p>Finally, a new deployment of NAVER Search was made available on August 31, 2023, improving web performance by changing the loading of JavaScript code to work based on the DCL event. After the deployment, the total LCP (p95) has been improved by 150 ms, from 2700 ms to 2550 ms.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*1UErHiItDX-kmTJSEoEUbQ.png" /></figure><p>The difference, 150 ms, may not be significant to users. However, repeated minor deteriorations in performance will lead to a severe risk at last and thus must be eliminated to make the service better.</p><p>This performance improvement process also let us understand that web performance metrics are not simply used to check performance. They can be used to identify how users can be affected by various attempts we make to run services reliably.</p><h4><strong>Conclusion</strong></h4><p>NAVER Search is constantly working on improving performance in various ways beyond those introduced in this article. As you can see in the following performance distribution graph of NAVER Search in 2023, the percentage of users with an LCP of 2.5 seconds or less decreased from 95% to 93% in June.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*TYs1aJKsq7J6w7ZB2p95-Q.png" /></figure><p>If we had not kept track of web performance metrics, we could not have understood what was going on and how to fix it. We have worked on improving web performance by introducing HTTP/3, enhancing UI/UX, and removing legacy code to align with the web performance guidelines of NAVER Search based on such data. As a result, the percentage of users with an LCP of 2.5 seconds or less increased to 95% at the end of the year.</p><p>Much of NAVER Search has been improved and we are still looking to advance, especially in the following topics. We hope anyone who is interested in these topics can join us and share their thoughts.</p><ul><li>Machine learning based performance prediction</li><li>Detect performance changes between versions and figure out the causes</li><li>Relationship between performance and business metrics</li></ul><p>In NAVER Search, we now use web performance metrics not only to simply gauge user-perceived performance but also to ensure service reliability. Furthermore, we are looking to analyze errors associated with web performance in detail and integrating them to enhance our service.</p><h3><strong>Web performance of NAVER Search</strong></h3><ul><li>Web Performance of NAVER Search — Data Collection and Visualization</li><li>Web Performance of NAVER Search — Monitoring and Performance Improvement</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8db383bf1462" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/web-performance-of-naver-search-monitoring-and-performance-improvement-8db383bf1462">Web Performance of NAVER Search — Monitoring and Performance Improvement</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[egjs 2024년 상반기 릴리즈 소식을 전해드립니다]]></title>
            <link>https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-0dfb8d0838bf?source=rss----3a0c875824ff---4</link>
            <guid isPermaLink="false">https://medium.com/p/0dfb8d0838bf</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[egj]]></category>
            <dc:creator><![CDATA[Malangfox]]></dc:creator>
            <pubDate>Fri, 05 Jul 2024 03:39:36 GMT</pubDate>
            <atom:updated>2024-07-05T06:04:07.187Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/315/1*KHP6jgO3ZfagJET2hqxw-w.png" /></figure><p>네이버의 FE 오픈소스 컴포넌트 그룹인 <a href="https://naver.github.io/egjs/">egjs</a>의 24년 상반기 릴리즈 소식을 전해드립니다.</p><p>이번 정기 릴리즈에서는 페이지 내 요소를 그리드 구성으로 정렬해서 보여주는 Grid 컴포넌트와 InfiniteGrid 컴포넌트에 추가된 새로운 기능과 이 기능을 사용하는 예시를 소개합니다.</p><p><a href="https://github.com/naver/egjs-grid">@egjs/grid</a> 와 <a href="https://github.com/naver/egjs-infinitegrid">@egjs/infinitegrid</a> 에서는 MasonryGrid, JustifiedGrid, FrameGrid, PackingGrid의 총 4가지 정렬 방식을 제공합니다.</p><p>이번에 추가된 기능은 한 줄에 높이가 균등한 여러 요소들을 표시하는 JustifiedGrid에 추가된 `stretch` 기능입니다.</p><p>— -</p><h4>🚀 JustifiedGrid에 새로운 기능 `stretch`가 이미지 검색에 들어갑니다.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KvJJsL7seSQWEF49PRZJcw.png" /></figure><p>JustifiedGrid의 특징이라면 화면에 꽉차면서 1줄의 아이템들은 높이가 균등하고 모든 아이템들을 여러 줄로 배치하는 방식입니다.</p><p>또한 dijkstra 알고리즘을 통해 아이템들의 비율을 유지하면서 너비를 채웠을 때 나오는 높이(cost)를 가장 최소화하여 배치하고 있으며 이미지 검색에서 주로 쓰일 수 있습니다.</p><p>하지만 기존 방식은 모든 아이템이 비율에 맞춰 배치하다 보면 극단적인 비율(3:1, 1:3)을 가진 아이템들이 존재하는 경우 1줄의 높이가 예상 범위 외로 커지거나 작아질 수 있습니다.</p><p>그렇기에 비율 왜곡, 최대사이즈, 최소사이즈 기능을 추가함으로써 문제점을 해결하고자 했습니다.</p><h4>요구사항</h4><p>1. 아이템의 높이가 228px로 고정 (이미지의 높이: 184px 고정)</p><p>2. 아이템 너비의 경우 가변 (최소 144px ~ 최대 320px)</p><p>3. 일부 아이템의 너비의 경우 첫 렌더링 됐을 때의 너비에 대해 +-10% 만큼 가변</p><p>4. 애매하게 남는 마지막 라인의 아이템들은 화면에 꽉 채우지 않아도 된다.</p><h4>신규 옵션 `stretch`?</h4><p>`stretch`기능은 JustifiedGrid의 확장 옵션으로 높이를 먼저 주어지며 아이템의 비율을 왜곡하여 너비 값을 조절할 수 있습니다.</p><p>그래서 높이가 정해졌을 때 왜곡된 아이템 사이즈(cost)를 최소화하여 배치하고 있습니다.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwiEJOszR1k5XK_Gw39ZiQ.png" /></figure><p>위 사진처럼 아이템의 사이즈는 왜곡되서 보여질 수 있지만 이미지의 사이즈는 왜곡되서 보여지면 굉장히 이상하게 보일 수 있습니다.</p><p>그래서 이미지에 `object-fit: contain;` 같은 속성을 추가함으로써 이미지의 비율을 유지할 수 있게 가능합니다.</p><p><strong>대신 margin이 생기지만 회색 배경 및 별도의 이미지 crop 또는 scale을 통해 이미지 처리가 들어갈 수 있습니다.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fyq6ePssSY28LuhA3E5U_g.png" /></figure><h4>동작 원리</h4><p>1. JustifiedGrid의 기본적인 동작으로 아이템의 비율을 유지하고 `inlineOffset`, `contentOffset`을 통해 이미지만 비율을 유지할 수 있습니다.</p><p>2. `stretch` 기능 활성화를 통해 높이를 고정했을 때 화면 너비보다 부족한/넘치는 만큼의 scale을 통해 아이템 너비를 변경합니다.</p><p>3. 너비 범위는 `stretchRange` 옵션 또는 개별 data attribute(`data-grid-min-stretch`, `data-grid-max-stretch`)를 통해 설정할 수 있습니다.</p><p>4. 너비가 min/max 도달하면 해당 아이템을 제외하고 다시 scale을 함으로써 화면을 꽉 채웁니다.</p><p>5. cost가 계산되지 않은 마지막 라인은 `passUnstretchRow`를 통해 stretch를 하지 않을 수 있습니다.</p><p>6. 모든 줄의 cost를 합하여 가장 적은 cost의 배치가 최종 배치가 됩니다.</p><h4>비교</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eDiDD1jy4UVgk6h4HSIulw.png" /></figure><h4>어떻게 사용하나요?</h4><p>JustifiedInfiniteGrid에 옵션들을 추가하면 됩니다. `stretchRange` 경우 개별적으로 옵션을 적용하고 싶다면 data attribute(`data-grid-min-stretch`, `data-grid-max-stretch`)를 통해 설정할 수 있습니다.</p><p>다음 주소에서 데모와 자세한 코드를 확인할 수 있습니다.</p><p><a href="https://naver.github.io/egjs-infinitegrid/storybook/?path=/story/examples-justifiedinfinitegrid--justified-infinite-grid-stretch-template">JustifiedGrid stretch 데모</a></p><p>— -</p><p>그 외에도 컴포넌트들을 사용하며 지원이 필요한 부분이나 안내가 필요한 부분들이 있다면 자유롭게 남겨주세요!</p><h3>🔖 egjs 릴리즈 내역</h3><h4><a href="https://naver.github.io/egjs-flicking/"><strong>@egjs/flicking</strong></a><strong> 4.11.3 (2024–05–31)</strong></h4><ul><li>`circular` 옵션이 활성화되어 있을 때 이벤트들이 잘못된 `direction`을 가지던 현상을 수정했습니다.</li><li>`bound` 옵션과 `align` 옵션을 함께 사용할 때 에러가 발생하던 경우를 수정했습니다.</li><li>`threshold` 옵션이 `movetype: snap`에 적용되지 않던 현상을 수정했습니다.</li><li>`destroy()`가 호출된 직후에 `resize()`를 호출했을 때 에러가 발생하던 현상을 수정했습니다.</li></ul><h4><a href="https://naver.github.io/egjs-grid/"><strong>@egjs/grid</strong></a><strong> 1.16.0 (2023–07–02)</strong></h4><ul><li>아이템들의 content 방향 정렬을 설정할 수 있는 `contentAlign` 옵션이 추가되었습니다.</li><li>가로 방향과 세로 방향의 gap을 다르게 설정할 수 있도록 gap의 type이 변경되었습니다.</li><li>아이템의 비율을 왜곡하여 너비 값을 조절하는 `stretch` 옵션이 추가되었습니다.</li></ul><h4><a href="https://naver.github.io/egjs-infinitegrid/"><strong>@egjs/infinitegrid</strong></a><strong> 4.12.0 (2024–07–02)</strong></h4><ul><li>리액트 환경에서 observer가 올바르게 작동하지 않던 현상을 수정했습니다.</li><li>아이템의 비율을 왜곡하여 너비 값을 조절하는 `stretch` 옵션이 추가되었습니다.</li></ul><p>— -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*uc-ZJmHAIeWdTz6RPHsJ8Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0dfb8d0838bf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/naver-fe-platform/egjs-2024%EB%85%84-%EC%83%81%EB%B0%98%EA%B8%B0-%EB%A6%B4%EB%A6%AC%EC%A6%88-%EC%86%8C%EC%8B%9D%EC%9D%84-%EC%A0%84%ED%95%B4%EB%93%9C%EB%A6%BD%EB%8B%88%EB%8B%A4-0dfb8d0838bf">egjs 2024년 상반기 릴리즈 소식을 전해드립니다</a> was originally published in <a href="https://medium.com/naver-fe-platform">NAVER FE Platform</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>