JavaScript Programming Framework

[svosam15-hub]

Приветствую, при открытии вкладки JavaScript Programming отображается белый фон, подскажите пожалуйста как исправить.

[Scavanger]

@sensei-hacker

https://github.com/iNavFlight/inav-configurator/blob/461824501f2d4445a2eeefa3ec229009b0baebca/tabs/javascript_programming.js#L42

Should be:

import('./javascript_programming.html?raw').then(({default: html}) => {
    GUI.load(html, () => {

https://github.com/iNavFlight/inav-configurator/blob/461824501f2d4445a2eeefa3ec229009b0baebca/js/transpiler/editor/monaco_loader.js#L28-L38

Vite doesn't work that way. In packed/deployed applications, there is no things like a /node_modules/ folder. Vite packs everything together into various .js files with cryptic names. Therefore, you cannot use path specifications in the renderer/browser, especially to load code. Monaco editor must be loaded via import in one way or another. Edit: This may help: https://www.npmjs.com/package/@bithero/monaco-editor-vite-plugin Edit 2: https://github.com/microsoft/monaco-editor/blob/main/docs/integrate-esm.md#using-vite Edit 3: #2445 Easier than first thought...

[svosam15-hub]

Спасибо за ответ но я не понял что конкретно нужно сделать для решения проблемы с загрузкой javascript. Нужно исходники исправить в node.js и заново собрать проект?

[Scavanger]

@svosam15-hub #2445 is merged. JS Programing in the latest nightly should now work.

[svosam15-hub]

Я использую последнюю версию 9 RC2. Если это не последняя версия отправьте пожалуйста ссылку с исправленной версией для скачивания

[sensei-hacker]

@sensei-hacker

inav-configurator/tabs/javascript_programming.js

Line 42 in 4618245

$('#content').load("./tabs/javascript_programming.html", function () { Should be:

import('./javascript_programming.html?raw').then(({default: html}) => { GUI.load(html, () => { inav-configurator/js/transpiler/editor/monaco_loader.js

Lines 28 to 38 in 4618245

// In Vite/browser environment, use relative path to node_modules // Vite will handle module resolution const monacoBasePath = '/node_modules/monaco-editor';

// Use the min build which includes everything const vsPath = monacoBasePath + '/min/vs';

console.log('Loading Monaco from:', vsPath);

// Monaco requires AMD loader, so use that directly loadMonacoViaAMD(vsPath, resolve, reject); Vite doesn't work that way. In packed/deployed applications, there is no things like a /node_modules/ folder. Vite packs everything together into various .js files with cryptic names. Therefore, you cannot use path specifications in the renderer/browser, especially to load code. Monaco editor must be loaded via import in one way or another. Edit: This may help: https://www.npmjs.com/package/@bithero/monaco-editor-vite-plugin Edit 2: https://github.com/microsoft/monaco-editor/blob/main/docs/integrate-esm.md#using-vite Edit 3: #2445 Easier than first thought...

Yeah thanks. I had actually made a commit fixing that too. :) But good to get your input since you actually know what you're talking about. :) I was fixing things just by aping what I saw.

[sensei-hacker]

Probably Friday or Saturday I will make a new RC, which will fix a couple issues related to JavaScript Programming.