Add Built-in Marketplace feature with direct downloads

[shdan-in]

Add Built-in Marketplace feature with direct downloads

Summary

This PR introduces a full built-in Marketplace feature to the editor with support for multiple content providers. It adds a unified browsing/import experience, provider-specific integrations (including authentication where needed), and a common provider architecture to make future marketplace sources easy to add. The goal is to let users search, preview, and import assets directly inside the editor without leaving their workflow.

Changes Made

Providers Included in this PR

• PolyHaven
• ambientCg
• Sketchfab

Marketplace

• Added a Marketplace module with a shared provider contract for search, asset details, authentication state, and download/import flow.
• Implemented provider registry/discovery so multiple providers can be enabled in a single UI.
• Added normalized asset/result models so different provider APIs map into a consistent editor experience.
• Added multiple marketplace providers with provider-specific API handling and mapping.
• Added OAuth support for providers like Sketchfab.
• Added asset download option handling (quality/type/format where available).
• Integrated marketplace downloads with editor import flow and file handling.

Benefits

• Users can discover and import assets from multiple providers without leaving the editor.
• Faster iteration: reduced context switching between browser and editor.

[shdan-in]

SKETCHFAB_CLIENT_ID needs to be setup in env for Sketchfab to work.

It can be requested from Sketchfab support page.

Submit following details:

Application name: BabylonJS Editor, Grant type: Implicit, Redirect URI: http://localhost:9542/sketchfab/callback , Username: BabylonJS Editor

For development I used mine.

[julien-moreau]

WOOOOOOOOOOOOW!!
I tried it and it worked so good!!!!!!!

I have suggestions and questions and I'm open to debate:

• As for support of Fab and Quixel I did, I would put this marketplace as a plugin: battle test it and see usage before we integrate it officially
• I think for materials we can go further: use "sharp" to merge metallic, roughness and ambient to create an ORM texture ready to use in realtime (we can't use metallic and roughness separately in Babylon.js PBR material)
• Even create .materials directly when importing textures if possible?
• Should we create sub folders like "assets/sketchfab", "assets/ambientCG" etc. so it's easier to navigate in downloaded assets for users? In case the output folder is "assets/"

For sketchfab, the client ID must be hidden or it can be seen once the app is packaged?

I really see the value of it and we all want it!! We can proceed step by step.
The release of Babylon.js 9 is coming in few weeks and I'm focusing on fixing bugs and improving stability first. Is going through a plugin a problem for you?

Also, did you use AI to generate it or you coded it by yourself or were you assited by AI? No judgement here don't worry just to know.

Can't wait to have your feedbacks and ideas

[julien-moreau]

One other suggestion: it is not possible to load HDRi from Poly Haven right now. In case you could add it, you could directly convert them to .env (https://doc.babylonjs.com/features/featuresDeepDive/materials/using/HDREnvironment#what-is-a-env-tech-deep-dive) directly so it's more optimized for the engine and less heavy

[shdan-in]

Thanks for all these suggestions, I will be adding these and more in future PRs, adding at once will make PR so big and harder to review for you too, so this only have Download functionality.

• I can move it to plugins, still some code will be needed at Editor like Oauth redirection. But I think marketplace should be core feature rather than a Plugin. No problem from my side to keep it as plugin though, your decision. Also, current plugin implementation needs a browser too😄.
• will add provider-based download subfolders
• Sketchfab ClientID can be packaged and seen
• Some part of it is AI assisted (not generated).
• HDRi are view only for now, I am figuring out a better way to handle subtypes (hrd/exr), so they are not included in allowed types yet

[julien-moreau]

Thanks for your answers!!

I did not understand "Also, current plugin implementation needs a browser too😄.". But I understand that it will still require the local webserver. Going through a plugin is not the solution then, keep your work in the core of the editor. I'm thinking what we can do.

[shdan-in]

What we can do is merge this after v9 release, so release is not impacted and this can be shipped in next release?

"Also, current plugin implementation needs a browser too😄" I meant we can add some plugin list to install from rather than manual npm package input

[julien-moreau]

"Also, current plugin implementation needs a browser too😄" I meant we can add some plugin list to install from rather than manual npm package input

FOR SURE!! And I already started it especially for the fab plugin as it is officially documented here: https://editor.babylonjs.com/documentation/plugins/fab

But finally I opt to have markerplaces in the core of the Editor as you were right since the beginning 😂

[julien-moreau]

What we can do is merge this after v9 release, so release is not impacted and this can be shipped in next release?

It depends. If integration of marketplaces is enough separated from main core features of the editor, it can be released for the version 9. For me it's also an opportunity to communicate for incoming features that may be tagged "exprimental"

[shdan-in]

It depends. If integration of marketplaces is enough separated from main core features of the editor, it can be released for the version 9. For me it's also an opportunity to communicate for incoming features that may be tagged "exprimental"

Let me work on separation of functionality a bit more to ship it as experimental. (Thinking to add a toggle in Editor settings to enable experimental features)

[julien-moreau]

It depends. If integration of marketplaces is enough separated from main core features of the editor, it can be released for the version 9. For me it's also an opportunity to communicate for incoming features that may be tagged "exprimental"

Let me work on separation of functionality a bit more to ship it as experimental. (Thinking to add a toggle in Editor settings to enable experimental features)

It's already done, you can use editor.state.enableExperimentalFeatures like here: https://github.com/BabylonJS/Editor/blob/master/editor/src/editor/layout/assets-browser.tsx#L812 =D
To activate/deactivate it you can open preferences (CMD+, on macOS or Edit -> Preferences... in main toolbar for Windows and Linux)

[shdan-in]

@julien-moreau Added HDRI support for PolyHaven, including direct converted import as ENV.
Also moved entire marketplace under experimental features

[julien-moreau]

@julien-moreau Added HDRI support for PolyHaven, including direct converted import as ENV. Also moved entire marketplace under experimental features

That's awesome! Really thank you I'm starting reviewing this week-end! I already had a look and it's really promising