Compatibility
Compile frameworks first#
Build TypeScript, JSX and frameworks first. Upload JavaScript; native languages are unsupported.
Builds inspect .js, .mjs, .cjs, .jsx, .ts and .tsx files. Typed and JSX syntax is preserved, not compiled. .mts, .cts, Vue, Svelte and native-language files pass through unchanged; compile them first.
JavaScript inside HTML scripts or event handlers is unchanged. Move it into a .js file to protect it. HTML asset links and markup finishing are handled separately.
Browser and Node.js apps are supported. Server-side beta currently targets browsers.
TypeScript and framework builds#
Vylocore does not replace TypeScript, JSX or your framework compiler. Run your usual application build first, then upload the deployable JavaScript and required assets. The tested workflow is TypeScript/JSX → normal application build → Vylocore → downloaded app. Existing source-level scanning/protection preserves supported typed syntax; it does not type-check or emit JavaScript. V3 executable selections require compiled .js, .mjs or .cjs files.
Electron and Tauri can use protection on their supported JavaScript layer. This does not protect Electron's native host or Tauri's Rust code. Test your actual preload/webview permissions and deployment; hosted server-side builds currently target same-origin browser applications. Node.js has offline V3 support. No native game-engine or anti-cheat support is implied.
For game-style apps, keep render, input and physics/update paths conservative or excluded. Protect valuable rules separately. A supported source file is not a promise that every transformation is safe for every function; required unsupported V3 selections fail instead of falling back to local JavaScript.
Check the scan#
Files ending in .private.json, including Gateway application keys and private backend reports, are omitted from customer build output. Keep them outside your deployment/source ZIP in the first place; they belong on your trusted server.
The scan shows which protections your code supports.
Keep generated files together. Function exclusions may skip file-wide finishing.
String protection also covers names accessed as obj['name'], class fields and switch cases. Import paths and fixed property names stay unchanged. Exclude a function if extra string work slows it down.
Source over the inspection limits fails a build when source protection is selected. Split large bundles or explicitly exclude them from protection. Reports list inspected source, unchanged source and assets separately; coverage counts eligible parts of inspected source, not the whole project.
Test the real app#
Test browsers, startup, async code, polyfills and Content Security Policy (CSP). Exclude busy functions if needed.