Quote from luishp on January 2, 2026, 7:21 pm

@mbpitt Yes, HTML / JavaScript / JSON can be used in VisualNEO Web, but you don’t “open” a Node project (node_modules) directly the way you would in VS Code.

VisualNEO Web projects are .neoapp files (XML), and you build your app by placing objects (pages, containers, buttons, etc.) and adding actions. For advanced work you can also edit the .neoapp directly with the built-in Source Code Editor.

Here are the practical ways to reuse what you already have:

1) If you already have an HTML page/app → use an iFrame (fastest)

If your existing app already runs in a browser, you can often embed it inside a VisualNEO Web app using an iFrame object and just set the source property to your URL (or hosted page).
This is the quickest “reuse without rewriting” option.

2) Paste small HTML chunks into VisualNEO Web objects

For smaller pieces of UI (formatted text, snippets, etc.) you can place content inside objects like Paragraph/Container (they support HTML editing).
Good for: layouts, formatted sections, simple embedded widgets.

3) Reuse JavaScript libraries by creating a VisualNEO Web plugin (best long-term)

If you have JS code (or a library) you want to call from NeoScript actions, the recommended route is to wrap it as a plugin:

• Use Tools → Plugin Generator

• Put your JS logic in the Code Tab

• Add any external JS files your code depends on in the Files Tab (they get bundled automatically)
  This is exactly how many built-in plugins work (wrapping popular JS libraries).

4) JSON usage: yes (multiple options)

VisualNEO Web has strong JSON support via commands/plugins. Examples:

• Load JSON from a server/API with neoAjax (supports JSON responses).

• Work with JSON structures and even generate forms from JSON Schema using neoJsonEditor.

So your .json files/data are definitely usable — the main question is where they come from (local file vs server vs embedded).

5) About node_modules

VisualNEO Web does not “import a Node project” or run Node the way a Node server does.

What you can do is:

• Bundle your Node-based code into browser-ready JS (e.g., with a bundler), then

• Include the resulting JS file in a plugin (Files Tab) or include it as an external script asset your app uses.

In other words: VisualNEO Web uses web runtime (browser), so Node-only modules (fs, path, etc.) won’t work unless you’re targeting a special desktop setup.

6) Advanced: edit the .neoapp directly (optional)

VisualNEO Web includes a Source Code Editor to edit the .neoapp XML, including embedding custom CSS/JS via tags like <CustomCSS> / <CustomCode>.
Useful if you know exactly what you’re doing (make backups first).

---

A simple rule of thumb

• Already working web app? → iFrame it.

• Need tight integration with NeoScript and VisualNEO actions? → make a plugin and bundle your JS files there.

• Have JSON data? → load it via neoAjax / manage it with JSON-oriented plugins.