New Releases: LeoJS 1.0.14 and LeoInteg 1.0.25

[Félix]

In sync with Leo 6.8.7, these releases bring major performance boosts, new @leo <path> support, and more!

🚀 LeoJS 1.0.14

This version brings major performance improvements and new features from Leo 6.8.6 and 6.8.7:

• A huge optimization: Opening skips unchanged @clean files. Leo keeps track of when it last wrote each external file with the _mod_time uA.
  
• Support for @leo <path> nodes: You can now include and link to other Leo outlines.
• New open-at-leo-file command and c.makeLinkLeoFiles() method to easily create top-level outlines linking to sub-outlines.
• New export-html-outline-viewer command: Export your outline as a fully self-contained, read-only HTML page with outline browsing, searching, hoisting, marking, and more.

🧩 LeoInteg 1.0.25

 - Added support for @leo <path> nodes (requires Leo 6.8.7).

You can grab those updates via auto-update, or manually from my VSCode Marketplace page or my Open VSX Registry for VSCodium page.

As always, feedback and testing are very welcome!
Félix

[Viktor Ransmayr]

Hello Félix,

Update of 'LeoInteg' & 'LeoJS' on Fedora 41 & Debian 12 worked w/o an issue for me.

Thanks a lot for these releases !

With kind regards,

Viktor

PS: LeoInteg's version number is already up to 1.0.26 ;-)

[Edward K. Ream]

On Tue, Oct 14, 2025 at 11:28 PM Félix <felix...@gmail.com> wrote:

As always, feedback and testing are very welcome!
Félix

Bwahahaha. Where did you get this picture of me?

Edward

[Zoom.Quiet]

Edward K. Ream <edre...@gmail.com> 于2025年10月15日周三 18:28写道：

> On Tue, Oct 14, 2025 at 11:28 PM Félix <felix...@gmail.com> wrote:
>
>> As always, feedback and testing are very welcome!
>> Félix

snap as atta.

extension always reboot,
and LEOJS always Starting up ..

VSCode error detail point->

Resolving extension issues with bisect
https://code.visualstudio.com/blogs/2021/02/16/extension-bisect

LEOJS not work in VSCode ?

>>
> Bwahahaha. Where did you get this picture of me?
>
> Edward
>

> --


--
----------------
life is pathetic, go Pythonic. 人生苦短, Python当歌 ;-)
俺: http://zoomquiet.io
大妈的多重宇宙 - https://www.youtube.com/@Chaos42DAMA
许: http://creativecommons.org/licenses/by-sa/2.5/cn/
怒: 冗余不做,日子甭过; 备份不做,十恶不赦; 格式兼容,无惧老化.
KM keep growing environment culture which promoting organization learning ;-)

[Félix]

Zoom.Quiet,  Thank you very much for this bug report :)


Can you please open the Developer Tools? You can do that by pressing CTRL+SHIFT+P and typing 'devel' like in this screenshot to then choose that entry:



This will open a panel that looks like a browser console similar to the screenshot below, can you spot some errors related to LeoJS when you open it? Please post what you see when you open that developer tools console:

This is what I see when I open some big Leo files, there is no bug on my machine so I'm very curious as to why it crashes on your machine! Those error in pink/red are comming from other stuff and are not a problem, but on your machine there should be error messages related to your instance of LeoJS that creashes and restarts repeatidly.


Thank you very much for helping fixing this! 

Félix

[Félix]

Dear Zoom.Quiet, Another test you could do if you can: 

Does this happen when opening vscode in a workspace where LeoJS tries to open file(s) upon loading? If so can you share that file for me to try with if it does not contain any sensible information? 

Can you try opening vscode by right-clicking in a new, empty folder, so that it is considered a workspace for which no .leo files will be automatically opened at startup. (LeoJS tries to reopen the last opened files PER WORKSPACE) When doing so, does LeoJS also crashes/reload in loop at startup even when starting up without trying to open any .leo files?

Here is what I mean:



And then this should open vscode with LeoJS without any pre-opened file (and hopefully without crashing):


Thanks for trying this out for me! :)

Félix

[Félix]

Here is yet another test you could do: Does opening vscode in the same workspace that crashes with 1.0.14 does actually also crash with the older 1.0.13 version? 

You could make sure of this by forcing the install of LeoJS to be the older 1.0.13 version like so (Click the down arrow on 'uninstall', this will offer to install instead an older version) : 



Thank you again for trying this to make sure you reliably reproduce the bug only with 1.0.14 and not 1.0.13. 

Félix