neo.mjs 9.14.0 → 9.15.0

package/ServiceWorker.mjs

@@ -20,9 +20,9 @@ class ServiceWorker extends ServiceBase {
          */
         singleton: true,
         /**
-         * @member {String} version='9.14.0'
+         * @member {String} version='9.15.0'
          */
-        version: '9.14.0'
+        version: '9.15.0'
     }
 
     /**

package/apps/portal/resources/data/examples_devmode.json

@@ -1,4 +1,11 @@
 [{
+    "id"          : 25,
+    "environments": ["Desktop", "Mobile"],
+    "image"       : "devmode/liquid-glass.png",
+    "name"        : "Liquid Glass effect",
+    "sourceUrl"   : "https://github.com/neomjs/liquid-glass-demo/blob/main/apps/myapp/view/GlassComponent.mjs",
+    "url"         : "https://neomjs.github.io/pages2/workspace/neo-liquid-glass-demo/apps/myapp/index.html"
+}, {
     "id"          : 24,
     "environments": ["Desktop", "Mobile"],
     "image"       : "devmode/bigData.png",

package/apps/portal/resources/data/examples_dist_dev.json

@@ -1,4 +1,11 @@
 [{
+    "id"          : 24,
+    "environments": ["Desktop", "Mobile"],
+    "image"       : "devmode/liquid-glass.png",
+    "name"        : "Liquid Glass effect",
+    "sourceUrl"   : "https://github.com/neomjs/liquid-glass-demo/blob/main/apps/myapp/view/GlassComponent.mjs",
+    "url"         : "https://neomjs.github.io/pages2/workspace/neo-liquid-glass-demo/dist/development/apps/myapp/index.html"
+}, {
     "id"          : 23,
     "environments": ["Desktop", "Mobile"],
     "image"       : "devmode/bigData.png",

package/apps/portal/resources/data/examples_dist_esm.json

@@ -1,4 +1,11 @@
 [{
+    "id"          : 23,
+    "environments": ["Desktop", "Mobile"],
+    "image"       : "devmode/liquid-glass.png",
+    "name"        : "Liquid Glass effect",
+    "sourceUrl"   : "https://github.com/neomjs/liquid-glass-demo/blob/main/apps/myapp/view/GlassComponent.mjs",
+    "url"         : "https://neomjs.github.io/pages2/workspace/neo-liquid-glass-demo/dist/esm/apps/myapp/index.html"
+}, {
     "id"          : 22,
     "environments": ["Desktop", "Mobile"],
     "image"       : "devmode/bigData.png",

package/apps/portal/resources/data/examples_dist_prod.json

@@ -1,4 +1,11 @@
 [{
+    "id"          : 24,
+    "environments": ["Desktop", "Mobile"],
+    "image"       : "devmode/liquid-glass.png",
+    "name"        : "Liquid Glass effect",
+    "sourceUrl"   : "https://github.com/neomjs/liquid-glass-demo/blob/main/apps/myapp/view/GlassComponent.mjs",
+    "url"         : "https://neomjs.github.io/pages2/workspace/neo-liquid-glass-demo/dist/production/apps/myapp/index.html"
+}, {
     "id"          : 23,
     "environments": ["Desktop", "Mobile"],
     "image"       : "devmode/bigData.png",

package/apps/portal/view/home/FooterContainer.mjs

@@ -107,7 +107,7 @@ class FooterContainer extends Container {
             }, {
                 module: Component,
                 cls   : ['neo-version'],
-                html  : 'v9.14.0'
+                html  : 'v9.15.0'
             }]
         }],
         /**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name"           : "neo.mjs",
-    "version"        : "9.14.0",
+    "version"        : "9.15.0",
     "description"    : "The webworkers driven UI framework",
     "type"           : "module",
     "repository"     : {

package/resources/data/deck/learnneo/pages/benefits/FourEnvironments.md

@@ -165,11 +165,21 @@ instant development flow.
 
 Understanding Neo.mjs's four distinct environments is crucial, but it's equally important to grasp how they interact,
 especially when your application needs to load additional, code-based modules dynamically—for instance, code written by
-users within a Monaco editor that contains its own import statements. These scenarios present a unique challenge: how
-does the framework ensure consistent and correct module loading across different deployment contexts?
-
-Neo.mjs's architecture handles this by defining specific loading behaviors for dynamically acquired code, ensuring
-compatibility while maintaining integrity:
+users within a Monaco editor that contains its own `import` statements. These scenarios present a unique challenge:
+How does the framework ensure consistent and correct module loading across different deployment contexts?
+
+For most traditional frontend frameworks relying on bundlers, handling such truly dynamic, run-time imports of
+"anything" (i.e., modules that aren't known at build time) is either impossible or astronomically expensive.
+Bundlers are designed to pre-analyze your application's static import graph and create optimized bundles or code-split
+chunks. To accommodate every possible module combination that could be dynamically imported at runtime would require
+generating an unmanageable number of split chunks, leading to insane overhead for internal bundler maps and a bloated,
+inefficient deployment.
+
+This is precisely where Neo.mjs comes to the rescue with its intelligent environment combinations – a novel approach
+that, to our knowledge, no other framework has truly accomplished. By leveraging native browser module loading
+capabilities and a sophisticated class registry, Neo.mjs ensures that even dynamically loaded code, with its arbitrary
+import statements, integrates seamlessly and efficiently into your application, regardless of the core environment
+it's running in.
 
 ### Loading Behavior for Dynamic Code Modules
 

package/src/DefaultConfig.mjs

@@ -264,12 +264,12 @@ const DefaultConfig = {
     useVdomWorker: true,
     /**
      * buildScripts/injectPackageVersion.mjs will update this value
-     * @default '9.14.0'
+     * @default '9.15.0'
      * @memberOf! module:Neo
      * @name config.version
      * @type String
      */
-    version: '9.14.0'
+    version: '9.15.0'
 };
 
 Object.assign(DefaultConfig, {