Mikael Svenson

@devromano Can you please open a support ticket for your case and provide trace logs when you log it?

@StevenDeRoover Please do it and share the id with me in some way.

@ceoper's fix together with `--always-gpu` solved it for me.

Haven't done any on-prem building with SPFx in years, so not sure how best to solve it. You could always spin up a new project and copy over the code.

And I want to bring the elephant into the room. Why do you need the web part? Just create a SPFx web part with the actual JavaScript code.

It's unfortunately built as a Windows XAML app way back. Try the search feature of this browser extension instead https://chrome.google.com/webstore/detail/sp-editor/ecblfcmjnbbgaojblcpmjoamegpbodhd Also see the blog post https://www.koskila.net/sharepoint-search-console-now-available-inside-chrome-sp-editor/

This adds into this change as well https://support.microsoft.com/en-us/help/4469277/sharepoint-online-search-will-not-return-private-onedrive-results where other random props should be supported as well.

If this is related to the PnP modern search web part, ask your question at https://github.com/microsoft-search/pnp-modern-search/discussions

Could be a good idea indeed. If time allows I'll take a look :)

There is no incremental crawl, only continous. Any queuing of full crawl/re-crawl will only have an adverse affect on indexing. A change on an item will be picked up automatically...