feat: making it work with wasm, moving json files into assets, fixing number deserialization on macos

Author: pavanpodila

claude.md

@@ -9,39 +9,12 @@ and interactive diagrams.
 - Flutter
 - Dart
 
-## Interactivity
-
-- Auto snapping when going close to an input port
-- Port stays within bounds of the node widget for perfect hit testing
-- Reliable hover effects and visual feedback for high-confidence interactions
-- No scaling effects on ports when hovering as they are jarring and don't work
-  well
-- All widgets and painting is done using values from the Theme objects for Node,
-  Port, Editor, Connection.
-- Capsule should rotate for top and bottom sides of Port. The core idea is that
-  the flat side of the half-capsule always stays on the outside.
-- The connection line should connect the outer edges of the capsule halves for a
-  smooth visual flow. This should work properly for both left/right and
-  top/bottom ports correctly.
-- The ports should be positioned on the edges of the node. For the left and
-  right ports, it will be horizontally centered on the left and right edges of
-  the node. For the top and bottom it should be vertically centered on the top
-  and bottom edges of the node.
-- Ports are always painted on top of Nodes so they are always visible
-- For the left/right nodes the port can be positioned starting from the top with
-  some offset from the top edge.
-- For the top/bottom nodes the port can be positioned starting from the left
-  with some offset from the left edge.
-- The temporary connection line painting is exactly like the actual connection
-  line painting. The line should connect the outer edges of the capsule halves
-  for a smooth visual flow.
-- Connections are established by clicking on a port and dragging to another
-  port. The connection is created when the user releases the mouse button on the
-  port and not as soon as the target port is hovered or snapped, but only when
-  dropped on the port. A drop anywhere else on the canvas should ignore the
-  connection.
-
 # State Management
 
 - Uses MobX for state management
 - Only raw observables, no annotations
+
+# Always Note
+
+- The Web Server or App is always running in the background
+- We are using Melos workspace so use its commands to bootstrap and update projects

justfile

@@ -1,13 +1,15 @@
+#!/usr/bin/env just --justfile
+
 set shell := ["fish", "-c"]
 
 # Build the Flutter web example
 build:
-    cd example && flutter build web --release --no-wasm-dry-run
+    cd packages/demo && flutter build web --release --wasm --no-wasm-dry-run
 
 # Deploy to Cloudflare Pages using Wrangler
 deploy: build
-    wrangler pages deploy example/build/web --project-name=vyuh-node-flow
+    wrangler pages deploy packages/demo/build/web --project-name=vyuh-node-flow
 
 preview:
-    cd example/build/web
-    serve -s .
+    cd packages/demo/build/web && \
+    serve . -s

packages/demo/.metadata

@@ -4,7 +4,7 @@
 # This file should be version controlled and should not be manually edited.
 
 version:
-  revision: "6fba2447e95c451518584c35e25f5433f14d888c"
+  revision: "adc901062556672b4138e18a4dc62a4be8f4b3c2"
   channel: "stable"
 
 project_type: app
@@ -13,11 +13,11 @@ project_type: app
 migration:
   platforms:
     - platform: root
-      create_revision: 6fba2447e95c451518584c35e25f5433f14d888c
-      base_revision: 6fba2447e95c451518584c35e25f5433f14d888c
-    - platform: web
-      create_revision: 6fba2447e95c451518584c35e25f5433f14d888c
-      base_revision: 6fba2447e95c451518584c35e25f5433f14d888c
+      create_revision: adc901062556672b4138e18a4dc62a4be8f4b3c2
+      base_revision: adc901062556672b4138e18a4dc62a4be8f4b3c2
+    - platform: macos
+      create_revision: adc901062556672b4138e18a4dc62a4be8f4b3c2
+      base_revision: adc901062556672b4138e18a4dc62a4be8f4b3c2
 
   # User provided section
 

packages/demo/analysis_options.yaml

@@ -0,0 +1,28 @@
+# This file configures the analyzer, which statically analyzes Dart code to
+# check for errors, warnings, and lints.
+#
+# The issues identified by the analyzer are surfaced in the UI of Dart-enabled
+# IDEs (https://dart.dev/tools#ides-and-editors). The analyzer can also be
+# invoked from the command line by running `flutter analyze`.
+
+# The following line activates a set of recommended lints for Flutter apps,
+# packages, and plugins designed to encourage good coding practices.
+include: package:flutter_lints/flutter.yaml
+
+linter:
+  # The lint rules applied to this project can be customized in the
+  # section below to disable rules from the `package:flutter_lints/flutter.yaml`
+  # included above or to enable additional rules. A list of all available lints
+  # and their documentation is published at https://dart.dev/lints.
+  #
+  # Instead of disabling a lint rule for the entire project in the
+  # section below, it can also be suppressed for a single line of code
+  # or a specific dart file by using the `// ignore: name_of_lint` and
+  # `// ignore_for_file: name_of_lint` syntax on the line or in the file
+  # producing the lint.
+  rules:
+  # avoid_print: false  # Uncomment to disable the `avoid_print` rule
+  # prefer_single_quotes: true  # Uncomment to enable the `prefer_single_quotes` rule
+
+# Additional information about this file can be found at
+# https://dart.dev/guides/language/analysis-options