Issues when building chrome debug extension about owl HOT 5 CLOSED

It should be solved, please report if you have further problems :)

from owl.

Hello, we are sadly unable to reproduce your problem even on a windows machine. Maybe try to remove all your local files and reinstall the repo.

from owl.

Hello, thanks for opening this issue.
This looks to be an issue that we currently have when building the extension from a Windows computer. @juliusc2066 is working on a fix that should be available soon :)

from owl.

fixed in #1405

from owl.

Hello,
I'm still having the issue, the complete traceback (some messages in french):

**Le chemin d’accès spécifié est introuvable.
created dist/devtools/page_scripts/owl_devtools_global_hook.js in 66ms

tools/devtools/src/content.js → dist/devtools/content.js...
created dist/devtools/content.js in 376ms

tools/devtools/src/devtools_app/devtools.js → dist/devtools/devtools_app/devtools.js...
created dist/devtools/devtools_app/devtools.js in 37ms

tools/devtools/src/utils.js → dist/devtools/utils.js...
created dist/devtools/utils.js in 29ms

tools/devtools/src/devtools_app/devtools_panel.js → dist/devtools/devtools_app/devtools_panel.js...
[!] Error: Could not resolve '../../assets/templates.js' from tools\devtools\src\devtools_app\devtools_panel.js
Error: Could not resolve '../../assets/templates.js' from tools\devtools\src\devtools_app\devtools_panel.js
at error (C:\Users\samin\OneDrive\Documents\GitHub\owl\node_modules\rollup\dist\shared\rollup.js:158:30)
at ModuleLoader.handleResolveId (C:\Users\samin\OneDrive\Documents\GitHub\owl\node_modules\rollup\dist\shared\rollup.js:22263:24)
at C:\Users\samin\OneDrive\Documents\GitHub\owl\node_modules\rollup\dist\shared\rollup.js:22257:26**

from owl.