Tencent EdgeOne Makers: Deploying a 3D AI Procedural Asset Studio with Next.js and Three.js
Building a web application is only one part of the development process. Once the application is ready, developers still need to think about deployment, performance, infrastructure, and how users can access the project reliably. For my project in the DevHandal 2026 Batch 2 program, I built a 3D AI Procedural Asset Studio, a web-based application that allows users to generate and manipulate simple…
Building a 3D AI Procedural Asset Studio using Next.js and Three.js requires careful consideration of deployment, performance, infrastructure, and user accessibility. To deploy the project, the author utilized Tencent EdgeOne Makers, a platform that supports modern web frameworks like Next.js.
The project, named Asset Studio, is a lightweight 3D workspace where users can interact with procedural 3D objects and generate or modify scenes using natural-language prompts. The application is organized as a pnpm monorepo, with the main web application located in apps/web and reusable functionality in workspace packages.
When preparing the project for deployment, the author kept the repository structure intact and used the pnpm build command for the web application. This ensures that the Next.js application correctly resolves internal workspace packages during the build process.
For deployment configuration, the author used the Next framework preset provided by EdgeOne Makers. This includes setting the Root Directory to ./ and specifying the Install and Compile Commands as pnpm install and pnpm --filter @asset-studio/web build, respectively.
After connecting the Git repository, EdgeOne Makers successfully completed the deployment pipeline, consisting of Initialize, Clone, Install, Build, and Deploy stages. The application is now accessible at https://threed-dpduaz9nfl3m.edgeone.dev/.
Key lessons learned include the importance of matching deployment configuration to the project architecture, especially for monorepos with dependencies outside the application directory. Additionally, understanding the difference between standard Next.js deployments and static exports is crucial in choosing the appropriate deployment mode based on the application's requirements.
To deploy a similar application, it is recommended to thoroughly understand the repository structure, configure EdgeOne Makers using the Next framework preset, and determine the appropriate deployment mode based on the application's functionality.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
