Runtime and Rendering Problems in `full` Template (windows)

[marcogomez-dev]

Issue: Runtime and Rendering Problems in full Template

Describe the Bug

After successfully creating and running the full template using Git Bash (to bypass the unzip error in windows), several runtime and rendering issues were observed without modifying the template code.

1. Missing Files/Routes: The backend server reports that certain expected .js files are not found upon startup:

   Not found /login/index.html.js
   Not found /@shared/ui/isomorphic.html.js
   

2. Incorrect Content Rendering: The content for the default docs and blogs views does not render correctly. The pages load, but the expected documentation or blog post content is missing or displayed improperly.
3. Cross-Tab Navigation Issue (Hard to Reproduce): A peculiar error occurred twice where clicking a link in one browser tab (e.g., navigating from /docs/ to /contact/) would cause the title of the active pages in other open tabs on the same server (http://localhost:4000/) to change to the title of the newly navigated page.

Environment

Aspect	Detail
OS	Windows 11
Nuekit version & JS runtime	Nue 2.0.0-beta.2 • Bun 1.2.23
Browser	Microsoft Edge

Minimal Reproduction

1. Use Git Bash to run bun run nue create full.
2. cd full
3. Run bun run nue.
4. Navigate to http://localhost:4000/.

To Reproduce Error 2.1 (Missing Files):

1. Check the server logs immediately after running bun run nue.

To Reproduce Error 2.2 (Intermittent Content Rendering):

1. Navigate to http://localhost:4000/docs/ and http://localhost:4000/blog/.

Logs & Additional Context

$ bun run nue
Nue 2.0.0-beta.2 • Bun 1.2.23
Model "leads" loaded (75 records)
Model "users" loaded (1 records)
Backend server started with 7 routes (reloadable)
Serving on http://localhost:4000/
Not found /login/index.html.js # Missing File 1
Not found /@shared/ui/isomorphic.html.js # Missing File 2

Visual Evidence of Missing Content (Error 2.2)

1. Blog View with Missing Post Content:

2. Docs View with Missing Documentation Content:

[marcogomez-dev]

Partial Solution: Path Normalization for Windows 🛠️

The issue with file assignment to collections has been identified as originating from an inconsistency in handling path separators on Windows within the file packages/nuekit/src/collections.js.

Cause

The matchPages function uses $\texttt{page.path.includes(pattern)}$ for its verification.

• On Windows, page.path uses the backslash (\).
• Collection patterns (in site.yaml) use the forward slash (/).

This character discrepancy causes the inclusion check to consistently fail, preventing files from being correctly assigned to their collections.

Proposed Solution

The solution is to normalize the file path by replacing backslashes with forward slashes prior to comparison, ensuring a successful match across all operating systems.

Proposed change in packages/nuekit/src/collections.js (matchPages function):

Before	After
javascript if (page.path.includes(pattern)) ret.push(page)	javascript if (page.path.replace(/\\/g, '/').includes(pattern)) ret.push(page)

This modification is expected to resolve the collections issue on Windows environments.

Note on the Solution Process

This change was generated and formulated with the assistance of Artificial Intelligence (AI).

The proposed solution for path normalization is based on logical and theoretical analysis. However, the testing performed to date has been superficial.

Thorough verification and testing are required for the implementation across various scenarios and environments (especially Windows) before it can be considered a definitive and permanent solution.

Page /docs/ after implementing the solution

[marcogomez-dev]

FIX: Windows Path Separator Compatibility 🛠️

🎯 Problem

The system's core logic (specifically asset resolution in nuekit/serve.js and script compilation in nuedom/compiler.js) expects forward slashes (/), conflicting with Windows' native use of backslashes (\). This led to:

1. Failure to load DHTML components.
2. Malformed JavaScript output due to line ending anomalies (CRLF) during script compilation.

---

✅ Proposed Solution

The solution introduces path normalization to ensure consistency across operating systems, along with special handling for Windows line endings (CRLF) in script compilation.

1. Path Normalization (in packages/nuekit/src/cmd/serve.js):

Backslashes (\) are replaced with forward slashes (/) before any path comparison.

--- a/packages/nuekit/src/cmd/serve.js
+++ b/packages/nuekit/src/cmd/serve.js
@@ -X,X +X,X @@
- return url.endsWith('.html.js') ? asset.path == url.slice(1, -3)
+ return url.endsWith('.html.js') ? asset.path && asset.path.replace(/\\/g, '/') == url.slice(1, -3)

2. Line Ending Handling (in packages/nuedom/src/compiler/compiler.js):

Carriage return characters (\r) are stripped to correctly process Windows line endings (CRLF).

--- a/packages/nuedom/src/compiler/compiler.js
+++ b/packages/nuedom/src/compiler/compiler.js
@@ -X,X +X,X @@
- `${key}: function() { ${expr.trim().replaceAll('\\n', '\n')} \n\t\t}`
+ `${key}: function() { ${expr.trim().replace(/\\r/g, '').replace(/\\n/g, '\n')} \n\t\t}`

---

🧪 Testing and Monitoring

Initial testing confirms successful loading of the /login DHTML component and no JavaScript syntax errors in the generated code.

Continuous monitoring and extensive cross-platform testing are recommended to ensure full compatibility across all Windows usage scenarios.

Note: This solution was developed and implemented with the assistance of Artificial Intelligence (AI) through systematic debugging and theoretical analysis of cross-platform compatibility issues.

Login page view after fixes