Release v2.3: Internal code refactoring

Internal Changes:
- Refactored monolithic analyzer.js into modular architecture
- Created src/ folder structure with organized modules:
  - src/core/ (config, analyzer, scoring)
  - src/detectors/ (content, framework, meta, performance)
  - src/ui/components/ (results-renderer)
- Bundled all modules into src/analyzer-bundle.js
- Updated popup.js and background.js to use new bundle
- Fixed script injection guard to prevent redeclaration errors

Version Updates:
- Bumped version to 2.3 in manifest.json
- Updated popup.html footer to v2.3
- Updated README.md version badge
- Added v2.3 entry to CHANGELOG.md

Technical Impact:
- No user-facing changes - functionality identical to v2.2
- Improved code maintainability and scalability
- Foundation ready for v3.0 feature development

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: dzienisz

CHANGELOG.md

@@ -5,6 +5,22 @@ All notable changes to the CSR vs SSR Detector extension will be documented in t
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.3] - 2025-10-20
+
+### Changed
+- **Internal code refactoring**: Split monolithic `analyzer.js` (350+ lines) into modular architecture
+  - Created `src/core/` folder with config, analyzer, and scoring modules
+  - Created `src/detectors/` folder with 4 specialized detector modules
+  - Created `src/ui/components/` folder for results rendering
+  - All modules bundled into `src/analyzer-bundle.js` for deployment
+- Improved code maintainability and scalability for future v3.0 development
+- Fixed script injection guard to prevent redeclaration errors
+
+### Technical Notes
+- No user-facing changes - functionality remains identical to v2.2
+- Better organized codebase makes future feature development easier
+- Foundation for v3.0 features (settings page, dark mode, export functionality)
+
 ## [2.2] - 2024-10-14
 
 ### Added

README.md

@@ -2,7 +2,7 @@
 
 [![Chrome Web Store](https://img.shields.io/chrome-web-store/v/fhiopdjeekafnhmfbcfoolhejdgjpkgg)](https://chromewebstore.google.com/detail/csr-vs-ssr-detector/fhiopdjeekafnhmfbcfoolhejdgjpkgg)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
-[![Version](https://img.shields.io/badge/version-2.2-blue.svg)](https://github.com/dzienisz/chrome-ssr-csr/releases)
+[![Version](https://img.shields.io/badge/version-2.3-blue.svg)](https://github.com/dzienisz/chrome-ssr-csr/releases)
 
 The **CSR vs SSR Detector** is a Chrome extension that helps developers and SEO specialists identify whether a webpage is rendered using Client-Side Rendering (CSR), Server-Side Rendering (SSR), or a hybrid approach. Understanding this distinction is essential for making informed decisions about SEO, page performance, and overall application architecture.
 

background.js

@@ -4,7 +4,7 @@ chrome.action.onClicked.addListener((tab) => {
   chrome.scripting.executeScript(
     {
       target: { tabId: tab.id },
-      files: ['analyzer.js']
+      files: ['src/analyzer-bundle.js']
     },
     () => {
       // After analyzer.js is injected, run the analysis

manifest.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": 3,
   "name": "CSR vs SSR Detector",
-  "version": "2.2",
+  "version": "2.3",
   "description": "Detect if a webpage is using Client-Side Rendering or Server-Side Rendering",
   "permissions": ["activeTab", "scripting", "storage", "notifications"],
   "action": {

popup.html

@@ -74,7 +74,7 @@ <h2><img src="icon.webp" alt="Logo">CSR vs SSR Detector</h2>
     <div id="result"></div>
 
     <div class="footer">
-      <p>v2.2 - <a href="https://github.com/dzienisz/chrome-ssr-csr" target="_blank">GitHub</a></p>
+      <p>v2.3 - <a href="https://github.com/dzienisz/chrome-ssr-csr" target="_blank">GitHub</a></p>
     </div>
 
     <script src="analyzer.js"></script>

popup.js

@@ -30,7 +30,7 @@ document.addEventListener('DOMContentLoaded', () => {
       chrome.scripting.executeScript(
         {
           target: { tabId: tabs[0].id },
-          files: ['analyzer.js']
+          files: ['src/analyzer-bundle.js']
         },
         () => {
           // After analyzer.js is injected, run the analysis