Build error about material-insiders version 9.5.3+insiders.4.48.0

[baytogi]

Hello all,
i am struggling about some issue which occurs only for "insiders" package. Here is the situation,
1- i am using the latest insiders version and pyhton 3.12.1
2- i can't build my website i am getting error like this. See the outputs.

3- If i install the non-insiders package than i am able to build successfully. See the outputs.

Why i am getting this error when i switch to the insiders version?

[squidfunk]

Thanks for reporting. Could you please create a minimal reproduction? If you could provide us with a runnable artifact, we can investigate and help you much more easily.

[squidfunk]

We can limit symbolic links to non-Windows systems for now, adding process.platform !== "win32". That should alleviate the problems until we find a better solution for the build system. I'm going to rework the build system at some point, but it's currently not a priority. However, I agree that we should ensure building works on all systems.

[baytogi]

Hi all, i am still waiting for a new release or suggestion about handling my issue. What is your suggestion for my insider building? i need to update my wiki page my i cant do it right now. Is there any workover for me?

[kamilkrzyskow]

Hi @baytogi,
a quick workaround for you would be to not use D:\0-GoogleDrive the issue comes from 2 different mount paths for the plugin internals and your files, due to a bug in the code. So you can just move the directory to the C: drive and everything should work as expected.
The PR should be merged into Insiders today or tomorrow after I add a small thing to it.
EDIT: C:\ has some issues with permissions on most Windows systems, so perhaps better use your C:\Users\baytogi\Documnets directory. You get the idea ✌️
EDIT2: You can also create a Virtual Environment https://docs.python.org/3/tutorial/venv.html in the D: partition and activate it when using D:\0-GoogleDrive

[squidfunk]

I just merged the PR, so you can try the latest master.

[baytogi]

Thanks for your replies. Latest merged PR solved the issue.