Comprehensive FlutterJS Framework Implementation with Material Design & Virtual DOM

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,48 @@
+---
+name: 🐛 Bug Report
+about: Report a bug to help us improve FlutterJS
+title: '[BUG] '
+labels: bug
+assignees: ''
+
+---
+
+## 🐛 Bug Description
+A clear and concise description of what the bug is.
+
+## 👣 To Reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '...'
+3. Scroll down to '...'
+4. See error
+
+## 👍 Expected Behavior
+A clear and concise description of what you expected to happen.
+
+## 📸 Screenshots
+If applicable, add screenshots to help explain your problem.
+
+## 💻 Code Sample
+Please provide a minimal code sample that reproduces the issue.
+
+```dart
+// Your code here
+```
+
+## ⚠️ Error Message
+If there is an error message, please paste it here.
+
+```text
+// Paste error message here
+```
+
+## 🌍 Environment
+- **FlutterJS version**: [e.g. 0.0.1]
+- **OS**: [e.g. macOS, Windows, Linux]
+- **Node.js version**: [e.g. 18.0.0]
+- **Dart version**: [e.g. 3.0.0]
+- **Browser (if applicable)**: [e.g. Chrome 114]
+
+## 📋 Additional Context
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,30 @@
+---
+name: 🚀 Feature Request
+about: Suggest a new feature or improvement
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+
+---
+
+## 🚀 Feature Description
+A clear and concise description of what the new feature is.
+
+## 💡 Use Case
+Describe the problem you are trying to solve or the scenario where this feature would be useful.
+
+## 🛠️ Proposed Solution
+Describe your proposed solution or implementation.
+
+## 🔄 Alternatives Considered
+Describe any alternative solutions or features you've considered.
+
+## 💻 Example Code
+If applicable, show how the feature would be used.
+
+```dart
+// Example usage
+```
+
+## 📋 Additional Context
+Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/widget_request.md

@@ -0,0 +1,30 @@
+---
+name: 🧩 Widget Request
+about: Request support for a specific Flutter widget
+title: '[WIDGET] '
+labels: widget
+assignees: ''
+
+---
+
+## 🧩 Widget Name
+Name of the widget you want ported from Flutter.
+
+## 🔗 Reference URL
+Link to the official Flutter widget documentation (api.flutter.dev).
+
+## 💡 Use Case
+Describe where and how you would use this widget in your web app.
+
+## ⚖️ Priority
+- [ ] **Critical** (Blocks development)
+- [ ] **High** (Needed soon)
+- [ ] **Medium** (Nice to have)
+- [ ] **Low** (Can wait)
+
+## 🤝 Willing to Contribute?
+- [ ] Yes, I can help implement this!
+- [ ] No, just requesting it.
+
+## 📋 Additional Context
+Add any other context or screenshots covering the widget's visual appearance.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,35 @@
+## 📝 Description
+Please include a summary of the change and which issue is fixed.
+
+## 🔗 Related Issue
+Fixes # (issue)
+
+## 🏗️ Type of Change
+- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
+- [ ] ✨ New feature (non-breaking change which adds functionality)
+- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] 📚 Documentation update
+- [ ] 🎨 Code style update (formatting, local variables)
+- [ ] 🔨 Refactoring (no functional changes, no api changes)
+- [ ] 🧪 Tests
+- [ ] ⚙️ CI/CD
+
+## 📋 Checklist
+- [ ] I have read the [CONTRIBUTING](CONTRIBUTING.md) doc
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## 📸 Screenshots (if applicable)
+| Before | After |
+| - | - |
+| <img src="" width="300" /> | <img src="" width="300" /> |
+
+## 🧪 How to Test
+1.
+2.
+3.

.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+  - package-ecosystem: "pub"
+    directory: "/"
+    schedule:
+      interval: "weekly"

.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: FlutterJS CI
+
+on:
+  push:
+    branches: [ "main", "master" ]
+  pull_request:
+    branches: [ "main", "master" ]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Dart SDK
+        uses: dart-lang/setup-dart@v1
+        with:
+          sdk: dev
+
+      - name: Install dependencies
+        run: dart pub get
+
+      - name: Verify formatting
+        run: dart format --output=none --set-exit-if-changed .
+
+      - name: Analyze project source
+        run: dart analyze
+
+      - name: Run tests
+        run: dart test

QUICKSTART.md

@@ -4,19 +4,20 @@ This guide shows you the **easiest ways** to run FlutterJS commands without typi
 
 ## 🎯 Quick Commands
 
-### Option 1: Using Wrapper Scripts (Easiest!)
+### Option 1: Global CLI (Recommended)
 
-**PowerShell (Recommended for Windows):**
-```powershell
-# From the flutterjs root directory
-.\flutterjs.ps1 run --to-js --serve
+First, activate the CLI globally:
+```bash
+dart pub global activate --source path .
+```
 
-# With verbose logging
-.\flutterjs.ps1 -v run --to-js --serve
+Then run commands from anywhere:
+```bash
+# Run dev server
+flutterjs run --to-js --serve
 
-# Other commands
-.\flutterjs.ps1 doctor
-.\flutterjs.ps1 build
+# Build for production
+flutterjs build
 ```
 
 **Command Prompt (cmd.exe):**
@@ -108,8 +109,8 @@ Most commands should be run from:
 
 ## 💡 Tips
 
-1. **Use `.\flutterjs.ps1`** for the quickest development workflow on Windows.
-2. **Access from anywhere**: Add `C:\Jay\_Plugin\flutterjs` to your PATH
+1. **Use Global CLI**: `flutterjs` is the fastest way to work.
+2. **Access from anywhere**: Provide full paths if running outside a project, or just cd in.
 3. **Check logs**: Use `-v` if something goes wrong.
 
 ---
@@ -118,10 +119,10 @@ Most commands should be run from:
 
 ```bash
 # Start development (simplest way)
-.\flutterjs.ps1 run --to-js --serve
+flutterjs run --to-js --serve
 
 # Build (production)
-.\flutterjs.ps1 build
+flutterjs build
 
 # Rebuild engine after changes
 cd packages/flutterjs_engine

README.md

@@ -88,13 +88,12 @@ FlutterJS compiles your Flutter/Dart code to **semantic HTML + CSS + JavaScript*
 npm install -g flutterjs
 ```
 
-### Option 2: From Source
+### Option 2: From Source (Development)
 
 ```bash
 git clone https://github.com/flutterjsdev/flutterjs.git
-cd flutterjs/packages/flutterjs_engine
-npm install
-npm link
+cd flutterjs
+dart pub global activate --source path .
 ```
 
 ---
@@ -591,6 +590,7 @@ PHASES 4-6: Converting IR to JavaScript...
 - [x] Engine Bridge (Dart CLI ↔ JS Runtime)
 - [x] Incremental compilation
 - [x] DevTools IR Viewer
+- [x] Dart Core Libraries (`dart:math`, `dart:async`, `dart:convert`, etc.)
 - [ ] Animation support
 - [ ] Full Material 3 theming
 - [ ] Route-based code splitting
@@ -600,6 +600,22 @@ PHASES 4-6: Converting IR to JavaScript...
 
 ---
 
+## Known Limitations
+
+### Method Tear-offs (Callback Context)
+Currently, passing methods directly as callbacks (tear-offs) may causing binding issues where `this` becomes undefined.
+**Workaround:** Wrap callbacks in a lambda to preserve context.
+
+```dart
+// ❌ Avoid (may fail based on transpiler version)
+onPressed: _incrementCounter
+
+// ✅ Recommended
+onPressed: () => _incrementCounter()
+```
+
+---
+
 ## Initialization
 
 To set up the project for development (both Dart and JavaScript packages), run the following command from the root directory:

SECURITY.md

@@ -0,0 +1,43 @@
+# 🛡️ Security Policy
+
+## 📦 Supported Versions
+
+| Version | Supported          | Notes |
+| ------- | ------------------ | ----- |
+| 0.0.x   | :white_check_mark: | Current development version |
+| < 0.0.x | :x:                | No longer supported |
+
+## 🐞 Reporting a Vulnerability
+
+We take the security of FlutterJS seriously. If you have discovered a security vulnerability, we appreciate your help in disclosing it to us in a responsible manner.
+
+> [!IMPORTANT]
+> **Please DO NOT report security vulnerabilities through public GitHub issues.**
+
+### How to Report
+
+Please email a detailed report to **[info@flutterjs.dev](mailto:info@flutterjs.dev)**.
+
+Include the following details:
+- **Type of issue** (e.g., XSS, Injection, logical flaw)
+- **Full paths** of source file(s) related to the manifestation of the issue
+- **Location** of the affected source code (tag/branch/commit or direct URL)
+- **Step-by-step instructions** to reproduce the issue
+- **Proof-of-concept** or exploit code (if available)
+- **Impact** of the issue, including how an attacker might exploit it
+
+### Our Response Policy
+
+1.  **Response**: We will acknowledge receipt of your report within **48 hours**.
+2.  **Assessment**: We will investigate the issue and determine its impact.
+3.  **Fix**: If verified, we will work on a fix and release a patch as soon as possible.
+4.  **Disclosure**: We will coordinate the public disclosure of the vulnerability with you.
+
+## 🔒 Security Best Practices
+
+When using FlutterJS in your applications:
+
+1.  **Secrets Management**: Never commit API keys or secrets to version control. Use environment variables.
+2.  **Input Validation**: Always sanitize and validate user input to prevent injection attacks.
+3.  **Dependency Updates**: Keep your dependencies up to date using `dart pub upgrade` and `npm update`.
+4.  **Transport Security**: Always use HTTPS in production environments.